-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AdGuard #15
Comments
Can you plug a display and look for errors during reboot? |
I tested again. The stats of the running services is about 30 - 40 min after reboot.
All services started directly by manual start except of these: I was no able to start nginx, to start letsencrypt and to restart dyndns. But I could not find helpful information in the log. Also login to web interface and to ssh was delayed and times out. But after about additional 10 min the hanging services suddenly started all is running smooth. Doing again a reboot, same happen again. |
If you want to protect your internal clients you can set any external nameserver in System : Settings : General, this will fix it |
Thank you. It helped partially. The timeout errors are gone. But still the services did not came up automatically. I will do some more testing the next days. Maybe it was not related to AdGuardHome. I cannot remember if I ever did a reboot since last OPNsense update. I found some more errors. Ngine needs al ong time to start. Is it possible that there is an binding issue for port 80 or 443 in combination with AdGuard? On purpose I use port 3000 for AdGuard and 4443 for the SSL port. Nor forwarding from http to https. But still. But looks like my issue is more nginx related than AdGuard.
|
I did some more testing. When I disable AdGuardHome and enable Unbound again on port 53 re-boot works fine. After 90 sec. my internet connection is up, I can get access to OPNsense via Webinterface using OPNsense itself as DNS for the host name. It takes a couple of more minutes and 100% of all services are up. When I change back, disable Unbound and enable AdGuardHome again on port 53 it is hanging again and services will not come up even after 1 hour. I do not yet know what is the root cause. It may not be AdGuard. But currently it is the "switch" to let the system run or not. |
Then just let it listen on port 5353 and add a port forwarding on LAN interface, with source LAN net and destination LAN address with port 53, portforward to localhost port 5353. |
OK. This is working. But seems to be not the clean way. Its more like a hack. Both unbound and dnsmasq allow to specify the interface to bind to. Only in AdGuard it seems to be not yet implemented to bind to more specific interfaces. Either 0.0.0.0 or one specific, but not multiple. As soon this will be the case you could add the bind host feature to the configuration page. |
No, because AGH has it's own UI for management and it would conquer with OPNsense, so there will only be an Enable checkbox. But you can jump to AdGuard project at github and ask for this feature over there? |
The topic "bind to multiple networks" I already found on GitHub #1401 AdguardTeam/AdGuardHome#1401 Me personally I will be fine to edit the config file. on OPNsense. |
Closing since upstream needs to work in this |
@mimugmail I'm noticing the same issue. For me, during startup OPNSense is trying to configure Dynamic DNS Clients: |
To follow up on this, I was able to get around the catch 22 by providing a 'fall-back' dns server (1.1.1.1) in |
DNS in System : Settings : General is used by local generated packets (like the process for dyndns), AGH is used by clients in your LAN so this should be ok |
I installed AdGuardHome on port 53 and disabled Unbound. All is running fine. But since this about. 50% of the services are not re-starting after OPNsense reboot. OPNsense is running 21.1.1.
The text was updated successfully, but these errors were encountered: