Adguard Home blocks different services

[yeraycito]

When installing and configuring Adguard and then restarting Opnsense, Adguard does not start as well as Cron, ddclient and Suricata. Once Opnsense is started, when Adguard is started, all other services start without problems.

[newsense]

AdguardHome takes time to load, especially on slower systems, and that will slowdown the startup of the others especially when large lists downloads/processing are expected to happen on boot.

Without more details that's my only take, and the screenshot you attached reflects it. A few more minutes and most/all services should be up.

The Download and Update Rules button in Suricata takes a very long time spinning, I would try removing Suricata from the picture and test again.

[yeraycito]

AdguardHome takes time to load, especially on slower systems, and that will slowdown the startup of the others especially when large lists downloads/processing are expected to happen on boot.

Without more details that's my only take, and the screenshot you attached reflects it. A few more minutes and most/all services should be up.

The Download and Update Rules button in Suricata takes a very long time spinning, I would try removing Suricata from the picture and test again.

Your comment is appreciated but I can assure you that you are wrong. Suricata is not the cause of the errors and my mini-pc is powerful enough, in fact Adguard always started before Suricata. Currently Adguard not only doesn't start when Opnsense is restarted, it blocks the other services from starting. Once Opnsense has been started and its interface has been accessed, until I start Adguard, the other services will not start.

[julsssark]

AdGuard is working fine for me on 23.7, but I am not running Suricata.

[36thchamber]

Any solution to this. Adguard is started so late in the boot process, that it blocks other internet-hungry services. The reason could be nothing running on port 53 to provide DNS.

[newsense]

Leave Unbound running on 53, move AGH to a different port and use a NAT - Port Forward rule applied to all interfaces in scope that would take outbound tcp/udp 53 and redirect it to 127.0.0.1 on the port where you moved AGH.

[Patrick M. Hausen]

Leave Unbound running on 53, move AGH to a different port and use a NAT - Port Forward rule applied to all interfaces in scope that would take outbound tcp/udp 53 and redirect it to 127.0.0.1 on the port where you moved AGH.

Seconded. I have

BIND on 127.0.0.1:53
AGH on 127.0.0.1:53530

AGH using BIND as upstream server

Port forward rules on all interfaces directing requests to BIND or AGH depending on what clients are connected to that particular interface.

In System > General I checked "Do not use the local DNS service as a nameserver for this system" and put 127.0.0.1 into the first name server field.

Never had a single startup problem caused by DNS.

[hushcoden]

Port forward rules on all interfaces directing requests to BIND or AGH depending on what clients are connected to that particular interface.

Would you mind to share those rules?

Tia.

[Patrick M. Hausen]

Would you mind to share those rules?

See screenshot. Port_DNS_AdGuardHome is 53530.

HTH,
Patrick