Skip to content
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

Closed
ghost opened this issue Jan 6, 2019 · 5 comments
Closed

v0.92-hotfix1 fresh install gives me 0 rules and is 'up to date' #533

ghost opened this issue Jan 6, 2019 · 5 comments
Labels

Comments

@ghost
Copy link

ghost commented Jan 6, 2019

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...?

screen shot 2019-01-06 at 3 40 43 pm

@ghost
Copy link
Author

ghost commented Jan 6, 2019

I was able to delete the SDNS filter and manually add it again which gave me a valid rule count.
But I wish I could force an update with the existing lists.

@ameshkov
Copy link
Member

ameshkov commented Jan 6, 2019

What did it print to the stdout when it was starting up?

@ameshkov
Copy link
Member

ameshkov commented Jan 6, 2019

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?

@ghost
Copy link
Author

ghost commented Jan 7, 2019

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?

@ameshkov
Copy link
Member

ameshkov commented Jan 8, 2019

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 1.1.1.1 or 176.103.130.130 once we expose the bootstrap DNS in the settings UI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant