Unraid Community App: Unable to Access AdGuard Home WebUI After Successful Installation

[NeZios]

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)

Custom (please mention in the description)

Installation

Docker

Setup

On one machine

AdGuard Home version

v0.107.40

Action

I've configured AdGuard Home on my Unraid server using Docker. The configuration included setting it up on the br0 network with a static IP address (192.168.1.15). The Docker run command used for the setup is as follows:

docker run
  -d
  --name='AdGuard-Home'
  --net='br0'
  --ip='192.168.1.15'
  -e TZ="Europe/Paris"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="FamilyBlanc"
  -e HOST_CONTAINERNAME="AdGuard-Home"
  -e 'TCP_PORT_3000'='3000'
  -e 'TCP_PORT_53'='53'
  -e 'UDP_PORT_53'='53'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://192.168.1.15:3000/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/SiwatINC/unraid-ca-repository/master/icons/adguard.png'
  -v '/mnt/user/appdata/adguard/workingdir':'/opt/adguardhome/work':'rw'
  -v '/mnt/user/appdata/adguard/config':'/opt/adguardhome/conf':'rw' 'adguard/adguardh

Expected result

I anticipated being able to access the AdGuard Home web user interface (webUI) upon successful installation. The logs indicated that the service was available at http://192.168.1.15:3000/ after the launch.

Actual result

However, despite the successful installation, I am unable to access the webUI using the provided address (http://192.168.1.15:3000/). The logs confirm the availability of the service at the said address, but attempts to access it fail.

Additional context: I use Wireguard VPN for remote tunneled access to my Unraid server.

I'd greatly appreciate any guidance, troubleshooting steps, or advice to resolve this issue and gain access to the AdGuard Home webUI.

Thank you for your support.

Additional information and/or screenshots

Using Unraid v6.12.4

[ainar-g]

Hello. Are you using a custom container or our official one?

The logs confirm the availability of the service at the said address, but attempts to access it fail.

To clarify, which logs do you mean here? AdGuard Home's? If so, have you enabled verbose logging?

[NeZios]

Hi @ainar-g
I am using the AdGuard Home on the Community App in Unraid

Here is the logs from adguard home after successful installation :

2023/10/29 22:40:31.042937 [info] AdGuard Home, version v0.107.40
2023/10/29 22:40:31.043184 [info] This is the first time AdGuard Home is launched
2023/10/29 22:40:31.043191 [info] Checking if AdGuard Home has necessary permissions
2023/10/29 22:40:31.043384 [info] AdGuard Home can bind to port 53
2023/10/29 22:40:31.044418 [info] safesearch default: disabled
2023/10/29 22:40:31.044920 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
2023/10/29 22:40:31.045617 [info] auth: initialized.  users:0  sessions:0
2023/10/29 22:40:31.045624 [info] AdGuard Home updates are disabled
2023/10/29 22:40:31.045626 [info] web: initializing
2023/10/29 22:40:31.045631 [info] This is the first launch of AdGuard Home, redirecting everything to /install.html 
2023/10/29 22:40:31.045638 [info] AdGuard Home is available at the following addresses:
2023/10/29 22:40:31.045858 [info] go to http://127.0.0.1:3000
2023/10/29 22:40:31.045864 [info] go to http://192.168.1.15:3000

Thanks for your help !

[ainar-g]

Ah, I see. Since it's not the official AdGuard Home Docker image, I'll transfer that to Discussions. You could also ask for help on the app maintainers' forums, if they have one.

[NeZios]

Wait, I think I have the official Adguard Home Docker Image as you can see here :

[NeZios]

Update: it works using host as network type.
But I want to use br0 to have AdGuard home his own IP address on my local network

Thanks for help.

[manicou537]

It's a little bit late, but I had the same problem and found a solution. I simply renamed the Working Directories and it worked right away.

[Jusaus]

Thanks! Worked like a charm, just added letter "s" to both working dirs and got it working.

[PhilippRoessner]

It's a little bit late, but I had the same problem and found a solution. I simply renamed the Working Directories and it worked right away.

this also worked for me, I tried for more than one hour to access the WebUI. is this a Bug?