Hi,
I am very confused.
Local PC that administers Pi-Hole now showing WebSite Blocked when trying to access Pi-Hole on Raspberry Pi.
I have been using Pi-Hole for a while on a Raspberry Pi 2 and now that is is running, decided to replace it with an older Raspberry Pi B+.
Installed Raspbian Jessie Lite, configured new Pi-hole and changed IP address to same as Current Pi-Hole.
Can ping OK, can SSH OK but if I try to look at it via a browser I get the following:
Website Blocked
Access to the following site has been blocked:
192.168.1.150
If you have an ongoing use for this website, please ask the owner of the Pi-hole in your network to have it whitelisted.
This page is blocked because it is explicitly contained within the following block list(s):
Go back Whitelist this page Close window
Generated Fri 3:17 PM, Jan 20 by Pi-hole v2.11.2
192.168.1.150 is the address of my Pi-Hole.
Restarted PC, flushed cache. Refreshed Browser to default. same problem.
I am able to get to it fine via Browser on another PC on my network.
Changed IP Address of Pi-Hole same issue, but still able to get to it from another PC.
Put old Pi-Hole back in and now I have the issue on both PC's.
"Website Blocked"
Checked through Pi-Hole lists and can not find any entries for my IP Addresses.
Is a MAC address being stored somewhere associated with my IP address and it being blocked.
Does my PC's not like the change in hardware, but if this is the case why is it supposedly the Pi-Hole that is throwing the error.
Those should return x-headers that identify as the Pi-hole.
What is odd is that we block via DNS name, and if you are visiting the site via IP address, there shouldn't be any blocking going on. So lets take a look at the debugger log.
Thanks for the reply,
Pihole -d done. Log uploaded. Token 2pelovawvn.
Hmmm Noticed that I still was on the changed IP address, changed it back to 192.168.1.150
Tried to web browse in the PiHole and it worked.
Very Embarrassing.
I don't know what has happened overnight with my system but it all seems to work again.
Sorry to have wasted your time.
Love the Pi-Hole keep up the good work.
Steve
apache2 up and running on port 80
Same issue on apache2.
Once I move lighttpd to port 80, lighttpd is not starting.
In the /var/log/pinhole_debug.log I found following
Daemon Process Information
Failure: IPv4 Port not in use <----------- !
Daemon Process Information
Found user dnsmasq with process dnsmasq
Processes Check
I also get the website blocked screen when I try to access http://192.168.2.xx (IP address of the pihole). I'm curious why this happens!? I'll try pihole -d