Warning at start when no DHCP dæmon configured: dhcpd: warning: creating dhcpv4 server err="dhcpv4: invalid IP is not an IPv4 address"

[mirabilos]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to report a bug and not ask a question or ask for help

• I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, ARMv6

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

just updated to latest

Action

I start AGH.

Expected result

No superfluous warnings.

Actual result

dhcpd: warning: creating dhcpv4 server err="dhcpv4: invalid IP is not an IPv4 address"

This occurs when no DHCP dæmon is configured, so naturally there’s no address for it to use.

Additional information and/or screenshots

The setup is that this is a normal host in the LAN that only acts as resolver, not as DHCP server; it’s got a static IP itself, and DHCP is handled by the gateway.

[tjharman]

I don't see this on my AdguardHome instance - I also have DHCP disabled.

Can you post the output from the dhcp: section of your config file please?
Mine looks like so:

dhcp:
  enabled: false
  interface_name: ""
  local_domain_name: lan
  dhcpv4:
    gateway_ip: 192.168.22.1
    subnet_mask: 255.255.255.0
    range_start: 192.168.22.10
    range_end: 192.168.22.20
    lease_duration: 86400
    icmp_timeout_msec: 0
    options: []
  dhcpv6:
    range_start: ""
    lease_duration: 86400
    ra_slaac_only: false
    ra_allow_slaac: false

[mirabilos]

On Sun, 19 Apr 2026, Tim Harman wrote: Can you post the output from the dhcp: section of your config file please?

Sure: dhcp: enabled: false interface_name: "" local_domain_name: lan dhcpv4: gateway_ip: "" subnet_mask: "" range_start: "" range_end: "" lease_duration: 86400 icmp_timeout_msec: 1000 options: [] dhcpv6: range_start: "" lease_duration: 86400 ra_slaac_only: false ra_allow_slaac: false

[tjharman]

Ok if you put some IP Address information in there like I've got?
It doesn't matter what it is, you can copy what's in mine, you're not enabling the DHCP Server.

[mirabilos]

On Sun, 19 Apr 2026, Tim Harman wrote: tjharman left a comment (AdguardTeam/AdGuardHome#8348) Ok if you put some IP Address information in there like I've got? It doesn't matter what it is, you can copy what's in mine, you're not enabling the DHCP Server.

This is what I got when disabling DHCP via the web UI. I guess putting IPv4 addresses in will fix the warning, but I’d rather have the code accept empty strings or JSON null for those fields, or not parse and emit it at all, if DHCP is disabled. Ideally, it would omit this from the config.

[tjharman]

Yes I agree I'm just trying to test if adding the IPs makes the warnings go away.
If we can confirm that, I'll raise this to devs to point it out.

[mirabilos]

On Sun, 19 Apr 2026, Tim Harman wrote: tjharman left a comment (AdguardTeam/AdGuardHome#8348) Yes I agree I'm just trying to test if adding the IPs makes the warnings go away.

It’s very likely it will (you could also try removing some from a setup without the warnings to see if they pop up).

If we can confirm that, I'll raise this to devs to point it out.

Hm, not tonight. I’ll try to find a time within the week in which I can do that (it’s an RPi1 on Debian armel that takes ages for everything).

[anartikov]

Yes I agree I'm just trying to test if adding the IPs makes the warnings go away.
If we can confirm that, I'll raise this to devs to point it out.

Description

I have a similar situation.

With the following settings (these were the default):

dhcp:
  enabled: false
  interface_name: ""
  local_domain_name: lan
  dhcpv4:
    gateway_ip: ""
    subnet_mask: ""
    range_start: ""
    range_end: ""
    lease_duration: 86400
    icmp_timeout_msec: 1000
    options: []
  dhcpv6:
    range_start: ""
    lease_duration: 86400
    ra_slaac_only: false
    ra_allow_slaac: false

I get this warning:

2026/04/20 05:22:21.971906 [info] dhcpd: warning: creating dhcpv4 server err="dhcpv4: invalid IP is not an IPv4 address"

If I change the settings to:

dhcp:
  enabled: false
  interface_name: ""
  local_domain_name: lan
  dhcpv4:
    gateway_ip: 192.168.22.1
    subnet_mask: 255.255.255.0
    range_start: 192.168.22.10
    range_end: 192.168.22.20
    lease_duration: 86400
    icmp_timeout_msec: 0
    options: []
  dhcpv6:
    range_start: ""
    lease_duration: 86400
    ra_slaac_only: false
    ra_allow_slaac: false

Then the warning disappears.

Notes

This behavior was present in version 73 and still occurs in version 74.
I never paid much attention to it since it is just a warning (info), not a critical error.

[mattxtaz2]

The main issue here is there is a "Reset settings" button on the DHCP screen which clears the config, thus causing this error. People reset the settings because they no longer wish to use DHCP, but then get this error in their log files on restart.

[tjharman]

The main issue here is there is a "Reset settings" button on the DHCP screen which clears the config, thus causing this error. People reset the settings because they no longer wish to use DHCP, but then get this error in their log files on restart.

Thanks for the clarification. I'll flag this to the devs.

[mirabilos]

On Wed, 22 Apr 2026, Tim Harman wrote: > The main issue here is there is a "Reset settings" button on the DHCP > screen which clears the config, thus causing this error. People reset > the settings because they no longer wish to use DHCP, but then get > this error in their log files on restart. Thanks for the clarification. I'll flag this to the devs.

Mind it’s not the clearing that is the error, but the parsing.