Description
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
Other (please mention in the description)
AdGuard Home version
v0.107.62
Action
Adguard Home is installed on a UnRaid system. DHCP handled by a router.
Adguard v0.107.62
Unraid v7.1.2
Local network: 192.168.x.y Subnet mask: 255.255.255.0
Router: 192.168.x.1
Adguard DNS: 192.168.x.2
Problem:
Starting adguard home GUI from the unraid "Docker Container" tab invoces a call to "192.168.x.2:3000" where the IP is correct but port 3000 gets blocked.
Removing the port from the address calls the GUI correctly.
Browser error message tells that connection to 192.168.x.2 is rejected.
MS EDGE ERR code = ERR_CONNECTION_REFUSED
Expected result
I would expect to have the container call the GUI page with the correct (80) or no port.
Actual result
Changing the PORT entry in the config menue to none or tho 80 does not change anything. GUI is still called via "192.168.x.2:3000"
Deleting the entry from the config menu does not change anything either.
Additional information and/or screenshots
No response