-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Whitelist Being Ignored completely (2.9.2 issue on Ubuntu?) #775
Comments
Hi, how are you adding the domains to the whitelist? Via commandline or via the web interface? |
And I do show that support is blacklisted on one of the lists:
|
I added it via the web interface Yeah i saw that too, not sure it should be but that's a discussion for another day. The weird thing is I know whitelisted sites were working Friday so I'm not sure outside of the update possibly what changed it. |
Okay, I'd like to move this issue over to the Web Interface repository for further review. Better venue to handle the questions. |
Issue moved to pi-hole/AdminLTE #159 via ZenHub |
I am having this issue again, is there any way to reopen this case as I was instructed to do if it re-appeared via the referenced issue above? It appears to be completely ignoring the whitelist entries again and I have to run pihole -g about 10 times before it starts working correctly. In the meantime while I do that they domains being blocked statistic on the web interface goes from 105k to 790, 340, 1 and then back up when it is fixed after running the -g command a ton of times. Any insight on what might be going on? My users are getting frustrated they can't see msn.com in the morning (but maybe that's a good thing :) ) |
Could you run off another |
Ok it has been uploaded to http://termbin.com/d4yd As another note I have run pihole -g multiple times and did a reboot after it looked fine and only got msn.com back. support.microsoft.com and www.msftncsi.com are still showing dns resolution to the pi-hole server. I did do multiple dns flush commands on the windows machines as well. |
OK, let's try rolling back to 2.9.1 and seeing if you still get the issue:
|
Ok, I have two pi-holes running right now both on different ips. I did this to the second one which is really only used in the case of a failure of the first one. I noticed after rolling back and doing a pihole -g that the domains blocked is 44k whereas the 2.9.2 primary which I have not rolled back yet is around 105k does that sound right? |
what does |
Hmm, could you pastebin |
Interesting, that one shoes 0 domains.... |
I also ran pihole -g after each one as well I believe a couple times. |
My word, now that I just ran it for that output it is up to 47k like the other one.... not sure why it was so low before... |
Ok, 2.9.1 seems to only pull in ~47k domains (Not sure why, I don't remember it happening at the time) I am unable to reproduce the whitelist being ignored, however, in both 2.9.1 and 2.9.2 |
So far I'm not having any issues with the whitelist being in 2.9.1 however it was fine yesterday after running the pihole -g a few times after letting it sit. Then this morning it was broke again. So at this point I'll let it sit the rest of today and will check in tomorrow and see if we get a replication of the issue. At least by Friday we should have an idea if it was something I was having an issue with in 2.9.2 or not Maybe then I can upgrade the secondary one again and we can test further with the primary on the "stable" version in my case. |
Hopefully we'll be up to 2.9.3 / 2.10 by the weekend (Don't hold me on that one though!) As we've been hard at work squashing some other bugs. |
Sounds great, thanks again for your help on this! |
still an issue with 2.9.3 for me |
|
Test case: support.microsoft.com The important snippets: I see a lot of errors in the webserver part: ####################################### 2016-10-17 19:41:46: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Notice: Undefined index: piholeIPv6 in /var/www/html/admin/data.php on line 3 ####################################### ####################################### ####################################### ####################################### ####################################### Oct 17 19:53:35 dnsmasq[159]: query[A] support.microsoft.com from [MYMACHINEIP] |
|
[MYPIHOLEIPv4] diagnostics.support.microsoft.com Edit: updating to 2.9.4 and removing gravity.list and all the list.X.. files and using pihole -g results in a total blocked domains of 99,870 while it used to be above 200k. Now the result of is: [MYPIHOLEIPv4] diagnostics.support.microsoft.com So,,, It's still being blocked via IPv6? |
@5an1ty For tracking, can you open a new issue with your current problem, it may be unrelated to the OP's problem. |
The development branch contains some changes to the way we apply the whitelists, so hopefully we should have any whitelisting issues fixed... (don't quote me on that 😉 ) |
I believe the issue that 5an1ty is describing is the same issue I am having as well. I'm in the process of updating to 2.9.4 after a hiatus to see if I see any improvement. |
The next version has a completely rewritten white and blacklist function. (It been merged to a single function and redundancy removed to help eliminate bugs.) The issue should be fixed in Master, but it definitely is fixed in development and will be released coming up shortly. |
Confirmed working in v2.9.5/v1.4.4.2 running on Ubuntu server 16.04.1. I had all sorts of problems both with Whitelists being ignored (trying to get Spotify on iOS to work) and domains being blocked going up and down between restarts. Everything seems fine now. Thanks! |
@sam24and48 did 2.9.5 fix the issue for you, too? |
I am updating right now and will begin testing to see if it did in fact work. I'll check back in shortly. Thanks! |
It is looking good so far. I am going to check it again in the morning to make sure but I think this version might have done the trick. |
It looks like that did the trick. Thanks again for getting that fixed and following up! |
You're welcome. |
This template was created based on the work of
udemy-dl
.In raising this issue, I confirm the following (please check boxes, eg [X]):
How familiar are you with the codebase?:
[FEATURE REQUEST | QUESTION | OTHER]:
{replace this section with your content or delete if not a FEATURE REQUEST/QUESTION/OTHER}
[BUG | ISSUE] Expected Behaviour: I have added multiple addresses including msftncsi.com, www.msftncsi.com, support.microsoft.com, and msn.com. We performed this last week and it fixed the issue of limited connectivity on our machines and also the ability to get to pages on support.microsoft.com and confirmed connectivity to msftncsi.com. (However today after the weekend and the 2.9.2 update it is pi-holing all of those addresses)
[BUG | ISSUE] Actual Behaviour: It appears to be completely ignoring the whitelist entirely. Today as I have done nslookups on the machines for all of those addresses they are pointing directly to the pi-hole ip. I have rebooted the pi-hole device multiple times along with dnsflushes on the machines multiple times. I can see in the web admin interface where it is flat out pi-holing the address when I go to it even though it is specifically added to the whitelist (example: support.microsoft.com).
[BUG | ISSUE] Steps to reproduce:
(Optional) Debug Log generated by
pihole -d
:http://termbin.com/s1lw
The text was updated successfully, but these errors were encountered: