AdGuard wont work on XE3000

Hey can everyome Show my log?

AdGuard wont start After restart in the Morning

AdGuardHome[25242]: 2025/09/28 08:34:04.690443 [info] AdGuard Home, version v0.107.66
Sun Sep 28 08:34:04 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:04.736362 [info] warning: no users in the configuration file; authentication is disabled
Sun Sep 28 08:34:04 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:04.757841 [info] tls_manager: using default ciphers
Sun Sep 28 08:34:04 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:04.771022 [info] webapi: initializing
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.727984 [info] dnsproxy: upstream mode is set mode=parallel
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.728107 [info] dnsproxy: cache enabled size=4096
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.728177 [info] dnsproxy: max goroutines is set count=300
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.728594 [info] dnsproxy: cache ttl override is enabled min=7200 max=86400
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.729115 [info] dnsproxy: ratelimit is enabled rps=20 ipv4_subnet_mask_len=24 ipv6_subnet_mask_len=56
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.729189 [info] dnsproxy: server will refuse requests of type any
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.729235 [info] dnsproxy: upstream mode is set mode=parallel
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.729284 [info] dnsproxy: cache enabled size=4194304
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.729337 [info] dnsproxy: max goroutines is set count=300
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.743976 [info] webapi: AdGuard Home is available at the following addresses:
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.746197 [info] go to http://127.0.0.1:3000
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.746298 [info] go to http://[::1]:3000
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.746332 [info] go to http://192.0.0.2:3000
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.746398 [info] go to http://[fe80::24c6:5abc:4442:d0e2%rmnet_mhi0]:3000
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.746426 [info] go to http://192.168.8.1:3000
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.746453 [info] go to http://10.5.0.2:3000
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.747702 [info] starting plain server server=plain addr=0.0.0.0:3000
Sun Sep 28 08:34:05 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:05.751448 [info] addrproc: processing addresses

AdGuardHome[25242]: 2025/09/28 08:34:23.816027 [info] dnsproxy: starting dns proxy server
Sun Sep 28 08:34:23 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:23.816204 [info] dnsproxy: creating udp server socket addr=0.0.0.0:3053
Sun Sep 28 08:34:23 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:23.816580 [info] dnsproxy: listening to udp addr=[::]:3053
Sun Sep 28 08:34:23 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:23.816669 [info] dnsproxy: creating tcp server socket addr=0.0.0.0:3053
Sun Sep 28 08:34:23 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:23.826266 [info] dnsproxy: listening to tcp addr=[::]:3053
Sun Sep 28 08:34:23 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:23.826597 [info] dnsproxy: entering udp listener loop addr=[::]:3053
Sun Sep 28 08:34:23 2025 user.notice AdGuardHome[25242]: 2025/09/28 08:34:23.827026 [info] dnsproxy: entering listener loop proto=tcp addr=[::]:3053

Aha. I solved it with a line that had to be written into the AdGuard init.d file.

I think this entry also belongs to:

MPTCP: mptcp need to implement this function: net/mptcp/subflow.c,subflow_v4_init_req,1791

procd_open_instance
procd_set_param respawn
procd_set_param group explict_vpn
procd_set_param stderr 1
procd_set_param env GODEBUG=multipathtcp=0
procd_set_param command /usr/bin/AdGuardHome --glinet -c /etc/AdGuardHome/config.yaml -w /etc/AdGuardHome -l syslog
procd_close_instance
[ -e /etc/edgerouter.fw ] && /etc/edgerouter.fw loaddns

Hello,

I didn't see what was wrong with ADG in the log you attached, seems the process was normal to start.

Glad to see that you have solved it later. Thanks!

Unfortunately, I don't have a picture of the ads being set to 0. It was working recently. The AdGuard interface wouldn't open anymore, and the ads were set to 0 for hours.

  1. Did you upgrade the ADG plug-in separately?
  2. Are there some plug-ins installed on the router? and it occupy ports 3000?
  3. Will reset the firmware be normal?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.