Works as Standard Installation...

[Trustwbc]

Hi, the description says that the data is admin/admin, which and 2 standard block lists are used by HaGeZi. UnBound and Redis are also used.

After installing the container via the Unraid app menu, I felt like I only had a standard instance of AGH. I first ended up at the installation manager, where I also had to assign the user and password myself. IP:3000 (IP:80 was unreachable)

The only thing that seems to be changed is Quad9 as the default upstream DNS server. Shouldn't Upsteam have IP:5335 / 127.0.0.1:5335 or something like that?

I also find no indication in the AdGuardHome.yaml that unBound is used.

Is there anything else that needs to be configured here? attached my yaml (as .TXT) file AdGuardHome.txt

[imTHAI]

Hello, It seems that you don't use the AdGuardHome.yaml included in the docker. Where did you find this one ? The default config folder is /mnt/user/appdata/adguardhome-unbound-redis (or /mnt/cache/appdata/adguardhome-unbound-redis) and the ADGH config file is here: /mnt/user/appdata/adguardhome-unbound-redis/AdGuardHome/AdGuardHome.yaml

In this file, the upstream server is the unbound server:

  upstream_dns:
    - 127.0.0.1:5335

And it's here in the WEBGUI:

I first ended up at the installation manager, where I also had to assign the user and password myself. IP:3000 (IP:80 was unreachable)

When you install the docker you have to assign a IP (let's say 10.0.3.12) and then the admin web page is http://10.0.3.12:3000

[Trustwbc]

No way... here Step-by-Step my new fresh installation (Live) / Custom IP: 192.168.2.10:

Brave: IP

Brave: IP:3000

DNS-Config:

Share:

Unbound added manualy :5335

And above my AdGuardHome.yaml (renamed as .txt File, becauce i cannot upload an .yaml File here) AdGuardHome.txt

[imTHAI]

Really strange. It works on my side. I hope I didn't miss anything before publishing. 😢 Can you try deleting the docker, then deleting all the config folder and subfolders: rm -rf /mnt/user/appdata/adguardhome-unbound-redis Then reinstalling the docker ?

I did it here, and I get the correct AdGuardHome.yaml

From the shell of the docker itself, I see ADG points to the file I've mentionned:

/ # ps aux
PID   USER     TIME  COMMAND
    1 root      0:06 /opt/AdGuardHome/AdGuardHome -c /config/AdGuardHome/AdGuardHome.yaml -w /config
    7 root      0:00 [redis-server]
    8 unbound   0:00 unbound -d -c /config/unbound/unbound.conf
   21 root      0:03 redis-server 127.0.0.1:6379
/ # touch /config/AdGuardHome/testfile

And from my unraid server I see the file (and the testfile I created from the docker):

# cd /mnt/user/appdata/adguardhome-unbound-redis/AdGuardHome
# ls -l 
total 4
-rw------- 1 root root 4013 Oct 21 11:09 AdGuardHome.yaml
-rw-r--r-- 1 root root    0 Oct 21 14:42 testfile
# grep -A1 upstream_dns: AdGuardHome.yaml
  upstream_dns:
    - 127.0.0.1:5335

[Trustwbc]

rm -rf /mnt/user/appdata/adguardhome-unbound-redis -> Check!

Then reinstalling the docker ? -> Check

After the Installation on a new IP Adress (192.168.2.11) i opend directly the Console in the Docker and the IP without :Port in the Browser:

Next i opened directly the AdGuardHome.yaml from /mnt/user/appdata/adguardhome-unbound-redis/AdGuardHome there i can see the :5335 as BootStrap Server

and the HaGeZi´s List;

But 192.168.2.11 doesn´t open. Also i stopped the Docker Container and changed the IP in the AdGuardHome.yaml manualy to: 192.168.2.11:80 in Line 5

Restart the Docker and:

The Solution is also the IP in the AdGuardHome.yaml is set to IP:80 (not 0.0.0.0:3000)

[imTHAI]

To make sure we understand each other, after installation, the default port is 3000, so if you want to be able to go to http://192.168.12.11 instead of http://192.168.12.11:3000, you need to modify the yaml file. In your first screenshot, when you run the grep command, I can see that you left the # in front of the command, so it didn't run. It understood this as a comment, that's why it gave no output. Anyway, the main thing is that your problem is finally solved. Have a nice day!

[Trustwbc]

To make sure we understand each other, after installation, the default port is 3000, so if you want to be able to go to http://192.168.12.11/ instead of http://192.168.12.11:3000/, you need to modify the yaml file.

Thats right. When i do not modify the yaml File, the IP is not reachable and i must enter IP:3000 -> but that starts a (new) Configuration and overwirtes your Config and unbound is not reachable.