-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
v0.92-hotfix1 fresh install gives me 0 rules and is 'up to date' #533
Comments
I was able to delete the SDNS filter and manually add it again which gave me a valid rule count. |
What did it print to the stdout when it was starting up? |
I mean could it be that when you first started it, there was no DNS available and that's why it failed to download the filter contents? |
I think I figured it out, your bootstrap_dns is 8.8.8.8:53 and I have Google DNS blocked on my router. Would this be the reason? Any reason why this isn't 1.1.1.1:53 out of curiosity? |
The problem with 1.1.1.1, in general, is that it is unavailable from some locations due to the history of the IP address. For instance, @hmage home ISP blocks it for some unknown reason. The second problem is that you can't change bootstrap DNS via the web admin interface, so we had to choose the most reliable DNS. We can change the default to |
When I fresh install v0.92-hotfix1 on my Pi, my rule count for AdGuard Simplified is on 0, even though the update time is when AdGuard Home was enabled and started.
Clicking on Check Updates refuses to update and tells me "All filters are already up-to-date".
Wish there was a way to force update...?
The text was updated successfully, but these errors were encountered: