AdGuard Home Binding Port on IPv6 Only

[Haravikk]

Prerequisites

• [X] I have checked the Wiki and Discussions and found no answer

• [X] I have searched other issues and found no duplicates

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

• [X] 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)

Darwin (aka macOS), AMD64 (aka x86_64)

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.107.50

Action

sudo lsof -PiTCP -sTCP:LISTEN | grep AdGuard

Expected result

AdGuardHome should be bound port 3000 on both IPv4 and IPv6

Actual result

AdGuardHome is only bound on port 3000 on IPv6, making it inaccessible by other machines on an IPv4 network:

AdGuardHo  160   root   99u  IPv6 0x9b74b5665d50fa17      0t0  TCP *:3000 (LISTEN)
AdGuardHo  160   root  104u  IPv6 0x9b74b5665d510657      0t0  TCP *:53 (LISTEN)

Additional information and/or screenshots

Not sure when this issue started occurring as I'm not sure what version I was on prior to updating, but it remains an issue; I have to go to each machine using AdGuard Home and connect using localhost:3000 locally, rather than connecting remotely as I normally would.

Here's what the top of my AdGuardHome.yaml file looks like on one affected machine:

http:
  pprof:
    port: 6060
    enabled: false
  address: 0.0.0.0:3000
  session_ttl: 720h

Seems like it should be correct, and I'm not seeing an options anywhere to configure for IPv6 only – if anything the address given would indicate IPv4 only surely?

[nathanialhenniges]

Am having this same issue.

[pieterburm]

anyone found what is wrong and have a solution?

[DarkG3n3sis]

same problem here.... i found that problem when qbittorrent stop working one day. i got this after an update.... . i previusly have installed this https://aur.archlinux.org/packages/adguardhome-bin by the aur, recently some pp added an official one on arch and i try to nuke my install of adg and installed the official one and on setup same problem, i port the confing.yaml after test and same problem obv. Is realy annoyng. P.s i have illiad, they give ipv6 and shared ipv4, but i think this is pointless to the problem

[Ducki]

Can confirm for the docker image as well.

[AchtungMoose]

downgrading to v0.107.57 resolves this. problem occurs from v0.107.58 onwards

[gtxaspec]

Hi, any update on this? @ainar-g any insight if this would be supported? force web port on ipv6 only?

it looks to support an ipv4 address only for address under the http category at the moment.