AdGuard Home (AGH) Port Conflict Resolution

AdGuard Home requires ports 53 (DNS) and 80 (Web Interface), but OpenWrt’s core services (Dnsmasq and LuCI) already use them. Use the following steps via SSH to fix the conflicts.

1. Resolve Port 53 Conflict (DNS)

We move OpenWrt’s Dnsmasq server from port 53 to port 5353, allowing AGH to take the standard port 53.

Stop AGH: /etc/init.d/adguardhome stop
Move Dnsmasq to Port 5353 (Execute these three lines): uci set dnsmasq.@dnsmasq[0].port=’5353′ uci commit dnsmasq /etc/init.d/dnsmasq reload
Configure AGH DNS Port: During the AGH welcome screen setup, set its DNS server port to 53.

2. Resolve Port 80 Conflict (Web Interface)

Since port 80 is used by LuCI and your reverse proxy, we change the AGH dashboard port.

Configure AGH Web Port: During the AGH welcome screen setup, change the Web interface port from 80 to an available port like 8080 or 81.
- Access: You will access the AGH dashboard via http://[OpenWrt_IP]:8080 (or the port you chose).

3. Finalize Traffic Redirection

Once AGH is set up and listening on port 53, you must redirect all DNS traffic hitting the router (which goes to Dnsmasq on port 5353) back to AGH on port 53.

Add a Forward Rule and Restart Dnsmasq (Execute these three lines): uci set dnsmasq.@dnsmasq[0].server=’127.0.0.1#53′ uci commit dnsmasq /etc/init.d/dnsmasq restart

4. Verification

Check the AGH dashboard at your chosen port (e.g., http://[OpenWrt_IP]:8080).
Ensure devices are successfully being filtered.

AdGuard Home (AGH) Port Conflict Resolution