Ok, I seem to be troubleshooting 2 different issues now. I think they are unrelated but let me know what you think:
Lighttpd & Dnsmasq both install/run without a problem and Pihole seems to be running fine but I can't get my Router (Fios Actiontec G1100) to propagate the new DNS setting. All devices still point DNS to the router/gateway after a reboot/network restart.
For clarity, in the router I'm setting the DNS to the PiHole/Synology IP at the following location (My Network -> Network Connections -> Broadband Connection -> Settings -> DNS Server). After a few router and client reboots, I couldn't get any client to show the new DNS settings.
Figuring this was just a router issue and wanting to test out PiHole, I moved forward setting the DNS settings on my Macbook client manually to the PiHole/Synology IP. This worked, (and wow was it fast, with no ads) but led to my 2nd issue...
I lost the Admin console. Wanting to see the stats page fill out, I went to see the admin console and got this:
Failed Host Check: pi.hole:8082 vs http://xxx.xxx.xxx.xxx, http://pi.hole, http://pi.hole, http://localhost
where xxx.xxx.xxx.xxx is the PiHole/Synology IP.
I should note that at some point today I ran
pihole -r and it updated to 2.10. This error only showed up after that. Not sure if it's a lighttpd error or PiHole error but Google comes up with nothing for either.
Again, ad blocking seems to be working - just can't see the admin console:
[email protected]:/# curl -i http://pi.hole:8082/admin/api.php?summary
HTTP/1.1 200 OK
X-Pi-hole: The Pi-hole Web interface is working!
Set-Cookie: PHPSESSID=3imohdj3r5b18m2i35q90sk7l3; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Content-type: text/html; charset=UTF-8
Date: Wed, 21 Dec 2016 21:27:06 GMT
Failed Host Check: pi.hole:8082 vs http://xxx.xxx.xxx.xxx, http://pi.hole, http://pi.hole, http:[email protected]:/#
Any ideas? thx!
Edit: seems I can't have more than 3 posts in this thread because I'm new. To answer the question in the next post, yes 8082 in the lighttpd.conf with a restart. Does 8082 go anywhere else?