What's new

AdGuardHome AdGuardHome New Release's 2023

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Maybe. ...I uninstalled scribe and Unbound and only use AGH with the scripts under my signature without any issues. If problems persist it might be time for a complete reset of router.
Is there any benefit of using unbound with AgH as only upstream server with regards to privacy? That was one of the reasons, plus if AdGuardHome breaks for whatever reason I don't lose internet, queries go through unbound.
 
Last edited:
Disabled scribe & skynet logging, seems ok so far even after reboot but syslog takes longer to load in the gui, shows nothing for some time.
 
Router GUI becomes unresponsive too so maybe running low on resources. Seems to become ok if I stop unbound. I'm going to remove it. Is there a way to have some sort of fall back DNS set on router if AdGuardHome breaks? Any way of routing DNS queries to the DNS servers set in WAN DNS Settings when AdGuardHome is down or it will automatically happen?
 
Last edited:
Removed unbound, rebooted. Still some problem. Also, I have google ntp server addresses in router GUI but looks like clock is still not getting set up on boot as I still see some entries from May 5. Something stops AdGuardHome
Code:
Aug  6 17:56:04 68U dnsmasq-dhcp[3647]: DHCPDISCOVER(br0) 90:9a:4a:17:ab:52
Aug  6 17:56:04 68U dnsmasq-dhcp[3647]: DHCPOFFER(br0) 192.168.1.25 90:9a:4a:17:ab:52
Aug  6 17:56:04 68U dnsmasq-dhcp[3647]: DHCPREQUEST(br0) 192.168.1.25 90:9a:4a:17:ab:52
Aug  6 17:56:04 68U dnsmasq-dhcp[3647]: DHCPACK(br0) 192.168.1.25 90:9a:4a:17:ab:52 Lamp
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.510134 [info] dnsproxy: starting dns proxy server
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.514269 [info] Ratelimit is enabled and set to 20 rps
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.516405 [info] The server is configured to refuse ANY requests
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.516616 [info] dnsproxy: cache: enabled, size 4194304 b
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.517301 [info] dnsproxy: max goroutines is set to 300
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.517666 [info] dnsproxy: creating udp server socket 0.0.0.0:53
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.518676 [info] warning: SO_REUSEPORT not supported: protocol not available
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.519086 [info] dnsproxy: listening to udp://[::]:53
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.519237 [info] dnsproxy: creating tcp server socket 0.0.0.0:53
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.519426 [info] warning: SO_REUSEPORT not supported: protocol not available
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.519757 [info] dnsproxy: listening to tcp://[::]:53
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.520324 [info] dnsproxy: entering udp listener loop on [::]:53
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.521120 [info] dnsproxy: entering tcp listener loop on [::]:53
Aug  6 17:56:09 68U S99AdGuardHome[2627]: Monitor is restarting AdGuardHome!
Aug  6 17:56:09 68U AdGuardHome[3053]: 2023/08/06 17:56:09.279019 [info] Received signal "interrupt"
Aug  6 17:56:09 68U AdGuardHome[3053]: 2023/08/06 17:56:09.279376 [info] stopping AdGuard Home
Aug  6 17:56:09 68U AdGuardHome[3053]: 2023/08/06 17:56:09.279530 [info] stopping http server...
Aug  6 17:56:09 68U AdGuardHome[3053]: 2023/08/06 17:56:09.279029 [info] service: action run has been done successfully on unix-systemv
 
Removed unbound, rebooted. Still some problem. Also, I have google ntp server addresses in router GUI but looks like clock is still not getting set up on boot as I still see some entries from May 5. Something stops AdGuardHome
Code:
Aug  6 17:56:04 68U dnsmasq-dhcp[3647]: DHCPDISCOVER(br0) 90:9a:4a:17:ab:52
Aug  6 17:56:04 68U dnsmasq-dhcp[3647]: DHCPOFFER(br0) 192.168.1.25 90:9a:4a:17:ab:52
Aug  6 17:56:04 68U dnsmasq-dhcp[3647]: DHCPREQUEST(br0) 192.168.1.25 90:9a:4a:17:ab:52
Aug  6 17:56:04 68U dnsmasq-dhcp[3647]: DHCPACK(br0) 192.168.1.25 90:9a:4a:17:ab:52 Lamp
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.510134 [info] dnsproxy: starting dns proxy server
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.514269 [info] Ratelimit is enabled and set to 20 rps
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.516405 [info] The server is configured to refuse ANY requests
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.516616 [info] dnsproxy: cache: enabled, size 4194304 b
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.517301 [info] dnsproxy: max goroutines is set to 300
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.517666 [info] dnsproxy: creating udp server socket 0.0.0.0:53
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.518676 [info] warning: SO_REUSEPORT not supported: protocol not available
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.519086 [info] dnsproxy: listening to udp://[::]:53
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.519237 [info] dnsproxy: creating tcp server socket 0.0.0.0:53
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.519426 [info] warning: SO_REUSEPORT not supported: protocol not available
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.519757 [info] dnsproxy: listening to tcp://[::]:53
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.520324 [info] dnsproxy: entering udp listener loop on [::]:53
Aug  6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.521120 [info] dnsproxy: entering tcp listener loop on [::]:53
Aug  6 17:56:09 68U S99AdGuardHome[2627]: Monitor is restarting AdGuardHome!
Aug  6 17:56:09 68U AdGuardHome[3053]: 2023/08/06 17:56:09.279019 [info] Received signal "interrupt"
Aug  6 17:56:09 68U AdGuardHome[3053]: 2023/08/06 17:56:09.279376 [info] stopping AdGuard Home
Aug  6 17:56:09 68U AdGuardHome[3053]: 2023/08/06 17:56:09.279530 [info] stopping http server...
Aug  6 17:56:09 68U AdGuardHome[3053]: 2023/08/06 17:56:09.279029 [info] service: action run has been done successfully on unix-systemv
Try uninstalling, and reinstalling. Please share here with us what settings you enable after reinstalling. I am wondering if you are enabling something or incorrectly configuring something not supported on the RTAC68U hardware because of this log

Aug 6 17:56:04 68U AdGuardHome[3053]: 2023/08/06 17:56:04.518676 [info] warning: SO_REUSEPORT not supported: protocol not available.

Also, please share the output of

netstat -nlp | grep "53"

Whenever you recieve this error.
 
Last edited:
Only enabling Optimistic caching & adding other quad9 dns servers, removing google dns servers, adding few blocklists. Can share .yaml file if that helps. Just got the error again. Do you want me to send you the full log? I still see May 5 on reboot first before time corrects, is that normal?
Code:
netstat -nlp | grep "53"
tcp        0      0 127.0.0.1:553           0.0.0.0:*               LISTEN      4747/dnsmasq
tcp        0      0 192.168.1.1:553         0.0.0.0:*               LISTEN      4747/dnsmasq
tcp        0      0 10.8.0.1:553            0.0.0.0:*               LISTEN      4747/dnsmasq
tcp        0      0 :::53                   :::*                    LISTEN      2596/AdGuardHome
udp        0      0 127.0.0.1:553           0.0.0.0:*                           4747/dnsmasq
udp        0      0 192.168.1.1:553         0.0.0.0:*                           4747/dnsmasq
udp        0      0 10.8.0.1:553            0.0.0.0:*                           4747/dnsmasq
udp        0      0 192.168.1.1:5351        0.0.0.0:*                           2133/miniupnpd
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           2148/avahi-daemon:
udp        0      0 :::53                   :::*                                2596/AdGuardHome
unix  2      [ ACC ]     STREAM     LISTENING       5352 1612/syslog-ng      /opt/var/run/syslog-ng/syslog-ng.ctl

Code:
Aug  7 10:43:01 68U watchdog: start ddns.
Aug  7 10:43:01 68U rc_service: watchdog 293:notify_rc start_ddns watchdog
Aug  7 10:43:01 68U custom_script: Running /jffs/scripts/service-event (args: start ddns)
Aug  7 10:43:02 68U ddns: update WWW.DNSOMATIC.COM default@dnsomatic.com, wan_unit 0
Aug  7 10:43:02 68U ddns: Clear ddns cache.
Aug  7 10:43:02 68U ddns: Start Inadyn(7).
Aug  7 10:43:02 68U custom_script: Running /jffs/scripts/service-event-end (args: start ddns)
Aug  7 10:43:02 68U inadyn[5077]: In-a-dyn version 2.10.0 -- Dynamic DNS update client.
Aug  7 10:43:02 68U inadyn[5077]: Update forced for alias all.dnsomatic.com, new IP# xx.xx.xx.xx
Aug  7 10:43:02 68U inadyn[5077]: Failed resolving hostname updates.dnsomatic.com: Name or service not known
Aug  7 10:43:02 68U inadyn[5077]: Will retry again ...
Aug  7 10:43:02 68U inadyn[5077]: Will retry again, rc=12
Aug  7 10:43:02 68U syslog: Error code 12: Temporary network error (DNS)
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.023973 [info] dnsproxy: starting dns proxy server
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.025456 [info] Cache TTL override is enabled. Min=2400, Max=84600
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.027552 [info] Ratelimit is enabled and set to 20 rps
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.028476 [info] The server is configured to refuse ANY requests
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.029393 [info] dnsproxy: cache: enabled, size 4194304 b
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.030763 [info] dnsproxy: max goroutines is set to 300
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.095249 [info] dnsproxy: creating udp server socket 0.0.0.0:53
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.106086 [info] warning: SO_REUSEPORT not supported: protocol not available
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.106540 [info] dnsproxy: listening to udp://[::]:53
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.106755 [info] dnsproxy: creating tcp server socket 0.0.0.0:53
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.107071 [info] warning: SO_REUSEPORT not supported: protocol not available
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.107350 [info] dnsproxy: listening to tcp://[::]:53
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.150138 [info] dnsproxy: entering udp listener loop on [::]:53
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.150639 [info] dnsproxy: entering tcp listener loop on [::]:53
 
Only enabling Optimistic caching & adding other quad9 dns servers, removing google dns servers, adding few blocklists. Can share .yaml file if that helps. Just got the error again. Do you want me to send you the full log? I still see May 5 on reboot first before time corrects, is that normal?
Code:
netstat -nlp | grep "53"
tcp        0      0 127.0.0.1:553           0.0.0.0:*               LISTEN      4747/dnsmasq
tcp        0      0 192.168.1.1:553         0.0.0.0:*               LISTEN      4747/dnsmasq
tcp        0      0 10.8.0.1:553            0.0.0.0:*               LISTEN      4747/dnsmasq
tcp        0      0 :::53                   :::*                    LISTEN      2596/AdGuardHome
udp        0      0 127.0.0.1:553           0.0.0.0:*                           4747/dnsmasq
udp        0      0 192.168.1.1:553         0.0.0.0:*                           4747/dnsmasq
udp        0      0 10.8.0.1:553            0.0.0.0:*                           4747/dnsmasq
udp        0      0 192.168.1.1:5351        0.0.0.0:*                           2133/miniupnpd
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           2148/avahi-daemon:
udp        0      0 :::53                   :::*                                2596/AdGuardHome
unix  2      [ ACC ]     STREAM     LISTENING       5352 1612/syslog-ng      /opt/var/run/syslog-ng/syslog-ng.ctl

Code:
Aug  7 10:43:01 68U watchdog: start ddns.
Aug  7 10:43:01 68U rc_service: watchdog 293:notify_rc start_ddns watchdog
Aug  7 10:43:01 68U custom_script: Running /jffs/scripts/service-event (args: start ddns)
Aug  7 10:43:02 68U ddns: update WWW.DNSOMATIC.COM default@dnsomatic.com, wan_unit 0
Aug  7 10:43:02 68U ddns: Clear ddns cache.
Aug  7 10:43:02 68U ddns: Start Inadyn(7).
Aug  7 10:43:02 68U custom_script: Running /jffs/scripts/service-event-end (args: start ddns)
Aug  7 10:43:02 68U inadyn[5077]: In-a-dyn version 2.10.0 -- Dynamic DNS update client.
Aug  7 10:43:02 68U inadyn[5077]: Update forced for alias all.dnsomatic.com, new IP# xx.xx.xx.xx
Aug  7 10:43:02 68U inadyn[5077]: Failed resolving hostname updates.dnsomatic.com: Name or service not known
Aug  7 10:43:02 68U inadyn[5077]: Will retry again ...
Aug  7 10:43:02 68U inadyn[5077]: Will retry again, rc=12
Aug  7 10:43:02 68U syslog: Error code 12: Temporary network error (DNS)
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.023973 [info] dnsproxy: starting dns proxy server
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.025456 [info] Cache TTL override is enabled. Min=2400, Max=84600
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.027552 [info] Ratelimit is enabled and set to 20 rps
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.028476 [info] The server is configured to refuse ANY requests
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.029393 [info] dnsproxy: cache: enabled, size 4194304 b
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.030763 [info] dnsproxy: max goroutines is set to 300
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.095249 [info] dnsproxy: creating udp server socket 0.0.0.0:53
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.106086 [info] warning: SO_REUSEPORT not supported: protocol not available
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.106540 [info] dnsproxy: listening to udp://[::]:53
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.106755 [info] dnsproxy: creating tcp server socket 0.0.0.0:53
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.107071 [info] warning: SO_REUSEPORT not supported: protocol not available
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.107350 [info] dnsproxy: listening to tcp://[::]:53
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.150138 [info] dnsproxy: entering udp listener loop on [::]:53
Aug  7 10:43:07 68U AdGuardHome[2596]: 2023/08/07 10:43:07.150639 [info] dnsproxy: entering tcp listener loop on [::]:53
Are you using a VPN?
 
Only enabling Optimistic caching & adding other quad9 dns servers, removing google dns servers, adding few blocklists. Can share .yaml file if that helps. Just got the error again. Do you want me to send you the full log? I still see May 5 on reboot first before time corrects, is that normal?

So ntp usually starts out as not set and will eventually be set. That is normal. You are welcome to share your .yaml file. Does you adguardhome continue to not work on some reboots, or does it eventually start to work?
 
So ntp usually starts out as not set and will eventually be set. That is normal. You are welcome to share your .yaml file. Does you adguardhome continue to not work on some reboots, or does it eventually start to work?
It's erratic. Sometimes doesn't work then works on next reboot.
 

Attachments

  • AdGuardHome.yaml.txt
    4.5 KB · Views: 35
I am starting to wonder if something is broken in adguardhome on the binaries for that model router. I just don't know the best way to report the issue.
So do you think unbound & scribe have nothing to do with it as I'd like to reinstall scribe, otherwise syslog fills up with skynet & other unnecessary logs?
 
I have noticed as of late, when you upgrade your associated firmware for your router, have a power cut or generally switch off and on the router Adguard will fail to load correctly. The only workaround I have done to solve it for myself is when it fails to boot in one of those circumstances is to do the following and invoke this command in SSH
Code:
killall -9 AdGuardHome S99AdGuardHome && service restart_dnsmasq
twice, to make sure.
then
Code:
reboot
Once a reboot has been done it starts and I can connect to the GUI.
 
I have noticed as of late, when you upgrade your associated firmware for your router, have a power cut or generally switch off and on the router Adguard will fail to load correctly. The only workaround I have done to solve it for myself is when it fails to boot in one of those circumstances is to do the following and invoke this command in SSH
Code:
killall -9 AdGuardHome S99AdGuardHome && service restart_dnsmasq
twice, to make sure.
then
Code:
reboot
Once a reboot has been done it starts and I can connect to the GUI.
You could just make sure you unmount your storage before flashing. This should trigger all entware services (including adguardhome) to stop running before you flash. It is always best to make sure you free up as much router memory as possible before ever flashing a new firmware. You can also invoke service stop_AdGuardHome Before flashing as well, but unmounting the storage and waiting for the ram to free up should do the same thing.
 
Hello all,
it seems as the installer does not want to start ;)

1699448251525.png
 
As of right now, we are at release v1.6.4
With this release, users can choose what port they wish to use for the AdGuardHome WebUI provided it is between the range "3000-65535" and not already in use by another process. Also, users should be able to reconfigure if they are tired of their present setup. However, this means essentially starting out fresh.
 
Last edited:
Getting this error updating to 1.6.5
/opt/etc/AdGuardHome/installer: line 736: syntax error: unexpected "then" (expecting "}")
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top