Pihole web interface not working after reboot. Nov 29 00:04:08 bpi-m2z systemd[1]: lighttpd.
Pihole web interface not working after reboot The expected behavior is that pihole should work. It was always working fine previously. I just installed a new router at home and everything was working fine except that the Pi had been working for over a year without a reboot. Roku 4 News Channels no longer working after Pi-Hole. , after reboot, the wg0 interface isn't up before Pi-hole is ready (more precisely, the pihole-FTL service is started), you may experience that Pi-hole doesn't listen on the Wireguard interface. Query isnt logging any website i visit and no ads blocked. Edit: Also, commands like ping/nslookup pi. service: Scheduled restart job, restart counter is at 5. I c Expected Behaviour: I had pihole running for about 2 years on an orange pi with no problems with the latest version. We use some essential cookies to make our website work. This seemed to be due to lighttpd not running. service lighttpd. Expected Behaviour: I got a raspberry pi zero to install pihole and unbound on it which were installed on a ubuntu server vm until now with zero issues. Never had this issue before. com/pi-hole/pi-hole/issues/2557 https://github. --purge autoremove -y sudo apt list --upgradable sudo apt update && apt upgrade -y && apt autoremove -y sudo systemctl reboot Greetings! Expected Behaviour: I recently installed pi-hole on my home server (Fedora 41/Intel Core i7). Expected Behavior: Web Interface for pihole expected to launch after initialization Hardware: -Raspberry Pi 3b+ -AlmaLinux 9 Actual Behaviour: Web address continuously produces, "unable to connect" Debug Token: TghyfJkb I did find two other discourse posts that pointed out improper ownership on certain directories, I followed those instructions to fix the Pi-hole not listening on wg0 after reboot¶ If, e. Before the update anything worked great. Expected Behaviour: DNS is working and pihole web UI shows stats in the dashboard Actual Behaviour: DNS not working, and web UI says "Lost Connection to API". Running in Docker with host networking Web port 9000 Expected Behaviour: The pihole to continue to run without issues Actual Behaviour: In the last two days, the pihole has stopped working after some time. net I connected to it via SSH and reset the password. service failed because a fatal signal was delivered to the control process. Even placing a static html file in the www root was returning an error, so I figured issue with broader than Pi-hole. Pihole is only used for visibility on dhcp and dns queries => blocking is disabled. From your debug log, even after a reboot, the web server works fine. The web interface might work with other web servers, but you will need to adapt your web server configuration. Remember, if you used the DietPi image, the Web interface is already installed. 1 - Web Interface v5. Then fails to run on next boot. 3) FTL version is vDev-78e0332 (Latest: v4. xxx" I've tried pinging. Also, even after issuing the command to restart DNS, the system reports that DNS is not running. I ran a diagnostic log while in this failed state. A blank page is shown when trying to load the dashboard. Reboot usually solves most of the problems. I tried a pihole -r it repairs fine, and pihole-d shows the expected x-header not available, and my web interface cannot be accessed. Debug Token: This issue can be immediately resolved by either SSH'ing in to the Pi and rebooting it, or following the steps to reboot through the PiHole's web interface (by navigating directly to its IP - pi. FTL v5. Blocked queries and procent is 0. system Closed January 10, 2023, 5:28pm 9. you can switch Pihole to Listen on all interfaces, permit all origins by running pihole -a -i all. The lighttpd is not running. Anudeep: lighttpd-enable-mod fastcgi i Updated my PiHole using "pihole -up" to the newest Version Pi-hole v5. hole I don't now why it's 127. php would come back with an err_empty_response. Method 1: Generate a debug token via the Web interface Log in to your Pi-hole's Web interface Navigate to Tools > Generate debug log Click the Generate debug log button Send us the debug token Method 2: Use the command line to generate a debug token Login into your Pi-hole's command line Enter pihole -d Provide us with the debug token that is generated after Upgraded to bookworm, web interface does not work anymore + pihole -r reports Unsupported OS detected: Debian 12 pihole -r [ ] Root user check . In order to to that, I followed those instructions: Enabling HTTPS for your Pi-hole Web Interface Setting up SSL with pihole, without a FQDN In the admin panel, I set a local dns to redirect pi. Debug Please follow the below template, it will help us to help you! Expected Behaviour: pihole dns service should automatically start after reboot Actual Behaviour: pihole service is starting normally but i have to manually restart dns service every time the machine is booted for other devices to connect to internet Debug Token: lpc8hcdryy Hi, i have been using pihole for Hi, I noticed a strange behaviour that I am not able to fix. service - Lighttpd Please follow the below template, it will help us to help you! Expected Behaviour: [Replace this text with what you think should be happening] Clients connect to network and are assigned an IP address Actual Behaviour: [replace this text with what is actually happening] Devices will not be assigned an IP, can only connect if they give a static IP. Click restart system and wait a few minutes. I have tried removing/destroying my container, and re-creating a new container; I have Hello I have some experience with pihole and up till now no issues. hole/admin, both are not working. service: Main process exited, code=exited, status=255/EXCEPTION Nov 29 00:04:08 bpi-m2z systemd[1]: lighttpd. When it came back up, it's handling DNS queries but nothing in the web interface is responding. Help. hole doesn't resolve in this situation). the web interface not working: The web server (lighttpd) is not running: *** [ DIAGNOSING ]: Pi-hole processes [ ] lighttpd daemon is failed But there are no errors on the log. This is what I get with "pihole -d" Hi everyone, as the subject already suggests my pihole doesn't working anymore after the update. Please go to your settings page and look at the Advanced DNS Settings. So I rebooted the pi-hole server. 3. This pihole runs on a raspi 4 8GB with twisterOS. pi-hole. The only thing I've done is order the 7" screen, and desktop case, and assembled it. net for sharing with developers only. Nov 16 08:52:47 pihole systemd[1]: Stopped Lighttpd Daemon. fresh install of a PiHole on a NanoPi black running Ubuntu1604 Expected Behaviour: Access admin interface by IP anytime without it going down Actual Behaviour: Admin/web interface works, then after maybe 30 seconds it goes down and doesn't come back yet PiHole is still blocking ads. Manage code changes Discussions. If I restart the DNS resolver using the GUI, everything works normally. What has This is a networking/OS level issue. I'm using Portainer for the deployment, but after the container comes up, the WebUI is not available, because of some trouble with lighttpd. If you are Experiencing issues with a Pi-hole install that has non-standard elements (e. Any ideas? I've checked for caplocks as well and specifically made them lower case to test. The log failed to upload to tricorder. I've scanned all existing discussion about the problem but actually no of them could provide me a solution. Today I modified some names of sensors in config file and then restarted HA ! It restarts from what I see in HA logs (loading sensors and everything and I don’t see any “interesting” errors in it but Web interface is down ! No more web access at HA ! I have already done a hard reboot of 127. Your RPi seems unable to connect to public addresses, presumably due to lack of proper routing. Expected Behaviour: Fully working PiHole setup Actual Behaviour: I have tried to do the following with no success: run 'pihole -r' to repair the setup uninstall with 'pihole uninstall' and reinstall Debug Token: [ ] ** FINISHED DEBUGGING! ** * The debug log can be uploaded to tricorder. PiHole itself is running correctly, however I am not able to get to the admin page and receive a browser 404. This did not changed the status. 1 itself seems to be blocked somehow. When my RPi reboots I have to manually run pihole restartdns before the DNS resolver will work. Please find the token below. service and post the output here. 2 LTS Hardware: Specification and hardware description of the Wyse 5070 (N11D) Thin Client 8GB Ram Intel Celeron J4105 (Quad Core) I installed pihole on my apache-based web server. Versions. Given that your debug log is normal, there is no obvious problem with Pi-hole. The pi-hole is configured with an IP in the 172. x range, but the domain name you listed is for an address in the 18. pi-hole is running on bananapi zero with Ubuntu 20. Actual Behaviour: After being online for 1-3 days, the DNS just got pihole set up on my already existing server. edit: And if you use pi. But probably something with my PiHole setting is wrong. 1 but it's work Check /etc/hostname it just says pi. 1 was available, along with the corresponding FTL and Web Interface. (I assume they are using other ports than 80, 81 and 443). The issue I am reporting isn't a duplicate (see FAQs, c After the reboot and before you run pihole restartdns, run sudo systemctl status --full --no-pager pihole-FTL. Until the next reboot. Hello I'm running pihole as docker container. EDIT Interestingly, though, I removed the variable from my docker-compose. hole, not via IP address. 3 AdminLTE: 5. This is my first help request. Inability to access via SSH is typically an OS level issue. I don't see anything in your debug log to pinpoint a cause, but your Pi-hole has been running for 3 days and the Pi-hole logs rotate nightly. Both Pis run pi-hole only. After a reboot of my Raspberry, it doesn't work anymore. Disable Apache (or use a different port for Apache) and run Pi-hole web interface using the default config. when i reboot my raspberry dns is not working until i restart dns server manually. Any clues on the issues? And how to solve it? I have three times rebooted my rp3 and now is working (PiHole). Actual Behaviour: Going to the admin page shows only a '403 - Forbidden' Message. Today I Hello, I have installed PiHole on a newly installed Debian 12. ubuntu/jammy container on Proxmox; Mac Mini late 2012; Actual Behaviour: /admin interface does not start with reboot, after I did apt upgrade and pihole -up. 15 - FTL v5. hole as a dns server also check in the Local DNS section of the pihole web interface that the name pi. 8. When I installed both pihole and unbound I restored the configuration Go to your pihole's IP address. 16. Here is my debug output: > > > *** [ INITIALIZING ] > Pihole was working fine using Router DHCP server, but I would like to see more details about which clients are hitting which external traffic sources. Using dig/nslookup just shows connection timed out. So. Have to "pihole restartdns" after reboot else start up normally as WireGuard is My Pi-hole server stopped blocking ads i noticed over the last week or so. I also can't access the pihole web interface (pi. xxx. Pi-hole was running good (for some months) and after a update no more web-interface was aviable. The text was updated successfully, but these How To Install The Interface. If you are searching for pihole problems, add "pihole" as a keyword. hole in the first line reboot if you made a change. 4) it started working again! Did not do anything aside from updating/reinstalling! since this upgrade, pi-hole web interface throws this warning after every reboot of the raspi: DNSMASQ_WARN Warning in dnsmasq core: interface eth0 does not currently exist everything seems to work and yes, the raspi Pausing pihole from web interface starts count down but websites are still blocked. ; These common fixes didn't work for my issue. So far, twice, pihole has randomly stopped working rendering the 2 test client devices disconnected from the Internet Web interface isn't visible, not via pi. x. Then click login. After restarting the Raspberry Pi 4 that runs Pi-hole, devices with Pi-hole set as their DNS do not load requested webpages. service: Service RestartSec=100ms expired, scheduling restart. Webinterface was working fine before running pihole - up but not anymore (did reboot Pi once). Ok, i had a problem like that before, so to my setup Raspberry pi 2, newest updates and upgrades Its running a Network bridge from lan to wlan I have 3 interfaces, eth0, br0, wlan0 the bridge is still working fine pihole is configured to use br0 for connections, working until reboot Now no SSH access is possible anymore Had someone the same problems? Internet Please upload a debug log and post just the token generated by. I tried rebooting it, as well as "sudo apt-get update", but still nothing. Collaborate outside of code Code Search pihole web interface display normally. 1 apt dist The Pi-hole VM requires a reboot every 1-3 days because everything just stops working for (apparently) no reason. Issue with pi-hole and dnscrypt on rpi4 after reboot I have recently connected a Raspberry Pi 3 Model B rev 1. 0. Both try to listen on port 80. sudo apt-get -y install php5-common php5 So, I've just spend the past day installing OMV on a spare system I had lying around to use it for random things, all was going smoothly with configuration and installation, I now have everything set up just how I like it with services such as PiHole and Docker, but, around an hour ago I rebooted the system from the webUI, and ever since I did this the webUI has not I appended those 2 lines into the existing pihole conf file under dnsmasq. I already did a debug for this pihole. d, ans also created new file and removing the entries from pihole, each time the rpi was rebooted, and previous to all of this, I changed the "Listen to all interfaces, permit all Origins" to "Listen to all interfaces". 1 ) at the same time. I tried [service lighttpd start] and it says "Starting web server: lighttpd" but when i check [service lighttpd status] again it says "lighttpd is not running . 1 pi. Clients e. Once you're logged in, click settings. Now, you are able to configure Pi-hole so you can securely access your Web Interface, and not cause issues with blocked HTTPS content. 13 FTL: 5. Filip_Gondro October 8, 2024, 4:48pm 1. What could Try clearing your browser's cache. The router uses another DNS, even though I've set both the primary and secondary to my Raspberry IP. I used pihole -a -p to delete the password. Pihole has been running for months without any issues (been absolutely rock solid), but since updating to v5 it will intermittently stop working and when I go to the web UI I see the "Lost Connection to Even though I find it strange that this procedure with the background download of the lists after the container restart does not work as well as with v5 (where the web interface / FTL was also active during the You signed in with another tab or window. Then click login again to submit the password. exhibitO March 8, 2018, 8:52pm 3. Unfortunately, this has noting to do with the slow dashboard loading. 168. yaml and resolv. I can, however, reach it if I use my IP address, instead. Restarting it and rebooting didn't help. systemctl status lighttpd. For further information: I did also an update on my synology Hello everybody, I've got a problem can anyone please help me? I'm not quite sure if my pi-hole is working correct because I still see ads (maybe a fewer but they are still there). `sudo service pihole-FTL start does not even work. Using either the IP or pi. com/pi-hole/pi-hole/pull/2816 After restarting the Raspberry Pi 4 that runs Pi-hole, devices with Pi-hole set as their DNS do not load requested webpages. Seems to work fine after running pihole -d. I am running on an Orange Pi Zero H2+. hole/admin URL. Just keywords and be specific, like "pihole not resolving DNS" instead of "why my pihole is not working". After the DNS server is restarted it immediately works. You should investigate your network startup sequence, e. Does the delay also appear when you try to access our Pi-hole over its IP address Apache 2 is likely the cause of the problem. 0 version , but after some time I cannot access the web admin portal. You signed in with another tab or window. 2 web ui works just fine. It is running on a Raspberry Pi Zero W. From local, curl myhostname:9080 did not work; From the host machine (running docker), curl localhost:9080 did not work; Verified the ports exposed by the container using docker ps | grep pihole on the remote machine; From inside the docker container (docker exec -it pihole bash), tried curl localhost and it did not work PiHole web interface not working . pihole status shows DNS service is running and Pi-hole blocking is En Interfaces that come up after pihole-FTL is running will not be recognized. Been struggling setting up a pihole (not an experienced Linux/networking person) and after successfully setting up the pihole, I can no longer access the web interface. Kernel: Linux 5. , the config option If I go into settings, DNS tab and then change the "Interface listening behavior" from "Listen on all interfaces" to one of the others, then back to "Listen on all interfaces" and press [save], it immediately starts working again. After a reboot, the system continues to work normally for awhile. Idk why there is two lighttpd daemons running on the host, only pih. when i try to access the web interface im After a Reboot the Pihole is not reachable but running. If I remove the password I can login. d or your cron jobs (maybe that's a Via web interface I performed a restart. PiHole as a DNS filter still working beautifully, but I just can't access the web interface. 5-458-g2de5362 (Latest: v4. Expected Behaviour: Going to the admin page/web interface should show stats etc. 1 Like. Expected Behaviour: Web interface will show information on Dashboard and Query Log on brand new install (raspberry pi 4 B, latest raspbian buster). All TCP/UDP services are not working. pihole restartdns doesn't change anything. The Pi-hole itself is working through ssh, everything works fine as it should, however can't access the WEB interface. [something] The page says "Pi-hole admin console". sudo service pihole-FTL status returns the Method 1: Generate a debug token via the Web interface Log in to your Pi-hole's Web interface Navigate to Tools > Generate debug log Click the Generate debug log button Send us the debug token Method 2: Use the command line to generate a debug token Login into your Pi-hole's command line Enter pihole -d Provide us with the debug token that is generated after This is not a supported config. If it does, do the same with the next one. I could then see various admin pages, but /admin/settings. I seem to have it working for answering DNS queries, but when I try to use the web interface, it just hangs, "Waiting for 172. alexiscordova reopened this May 4, 2018. When I Funny thing is, somehow my phone is connected to the ruined Pi-hole and wi-fi icon is on. service" and "journalctl -xe" for details. Web access seems to stop working during installation process of PiVPN somwhere during Rebooted my Pi-hole today and when it came back up the web interface was showing "Lost connection to API" at the top, as shown here: Taken from Both were upgraded (Pi-hole v5. my other computers will still open pages on www. There wasn't - the same lighttpd pid was listening on port 80 for IPv4 as well as IPv6. log [2020-05-16 00: Pinging 8. 11. Previously, I had this set to only listen on the eth0 interface (I only use a wired connection), however now when I chose this, and reboot my Pihole, I get a message that eth0 is an unknown interface. I got frustrated and just downloaded a new DietPi image and reloaded the image onto I recently updated my Pihole to the latest, and noticed a new setting in the interface section. hole/admin says it’s Don't ask me why a reboot or shutdown didn't work, but that CLI did. I have no issues with the web interface. I suspect the lighttpd . no information no help The use of crystal balls & mind reading are not supported Currently whitelisting a domain through web interface doesn't work. The issue I am reporting can be replicated. For me this is fixing the issue and PiHole is working right after a reboot. 04. This can be mitigated by artificially delaying the start of Pi-hole using, e. Hi I had the same boring problem. Rather, access to 1. hole/admin or ip/admin Actual Behaviour: I can't open the web interface. (When I install pi-hole inside of a Ubuntu 14 VM on ESXi, it Expected Behaviour: I should be able to open the web interface with pi. Enter pihole -w android. d/lighttpd restart" sCHween January 12, 2017, 6:11am 10. That works. What system is your Pi-hole working on? A Raspberry PI? Hmm, this is quite mysterious that you can ping the Pi via its IP + its host name but you cannot access the web interface, At last "/etc/init. So, assuming you used the automated install command to install the Pi-hole, run the following commands to add the Web interface to your setup: Install and enable PHP, needed for the interface. After trying some things out (like pihole -r, uninstalling and reinstalling, changing settings on the admin site, using both eth0 and wlan0) I seem to have made the issues worse because now I can't even access the admin site Team, I'm running Pihole on a VM (no docker) with Ubuntu 20. I've tried 3 different passwords and none of them work. I try that password and it doesn't work. Now it no longer works. The only way to bring that service online is to issue the command sudo service pihole-FTL restart . However, I went to log in to the web interface (first from remote, then logged into my Raspberry Pi) but it will not log in. your docker run command, pages to visit, CLI commands you ran. gregsdennis May 18, 2019, 12:24pm 3. 04 with NGINX for serving multiple sub-domains What I have changed since installing Pi-hole: I am just updating the standard Nov 16 08:52:47 pihole systemd[1]: lighttpd. Any clues on the issues? And how to solve it? Thanks. Pi Hole Web Interface Not Working (lighttpd issue?) Sat Jun 29, 2019 2:12 pm . Hi Running HA up-to-date in hassio on Pi 3B+ working since a while like that. 2-457-g0a81dadf (Latest: v4. Actual Behaviour: I'm still testing it but facing issues with stability. After entering the dns of the raspberry pi on which the pi-hole is placed into the router No, not that I recall. What Plan and track work Code Review. I have installed PiVPN with Wireguard option, DNS requests through VPN goes to PiHole. hole host, or assign an IPv4 A record only, no AAAA record for pi. or you can run pihole status manually after reboot. Actual behavior / bug. Either remove Apache2, or configure Pi-hole to listen on a different port. Pi-hole Userspace Web interface is not working. Actual behavior: token} Rebooted server, already at latest version or would upgrade {Steps of what you have done to fix this} Just reboot really. hole. There is not a single valid reason to do that. My admin console became inaccessible through browser after PiVPN installation. I have to open the pihole admin page from my computer first (not possible from tablet or cellphone) before any of the In raising this issue, I confirm the following: {please fill the checkboxes, e. 1 demonstrate that this is not to due to Pi-hole's DNS resolution or DNS in general. Below is my docker How can I enable HTTPS (SSL/TLS) for my Pi-hole Web Interface? Many users run their Pi-hole on Virtual Private Servers and such, meaning that they would need to access the Web Interface via insecure HTTP. pihole -d allowing to upload when prompted, or do it through the Web interface: Tools > Generate Debug Log Oct 23 19:14:32 nuc pihole-FTL[1004]: dnsmasq: unknown interface eno1 pihole-FTL cannot start because its network interface isn't available. It serves as the DNS for two devices with which I'm testing pihole. I was expecting to be able to log into the web interface to begin my I created a new group and added my work laptop to it, my adlists only apply to the default group and not work group. ;;,. The issue is resolved after repairing with pihole -r, but reoccur again after restarting the Raspberry Pi. So I wanted to check if everything is working fine: I opned the dashboard and the only information I see are just the "infinity loading circles". I gave up on tshooting this, it will suddenly restart working after some time. Pi-hole contains lighttpd as a dedicated web server. Since then it stopped working. Jun 25 21:03:48 raspberrypi systemd[1]: Stopped Lighttpd Daemon. Each time I have to reboot my server or restart pihole, I have to go in and reset its password. I'm just having a look into the Pi-hole options how this is generally done, and which IPs are assigned automatically. There is no standalone dnsmasq in the system. It's probably 192. The issue I am reporting isn't a duplicate (see FAQs, c 2. log I see that pihole is working. Options: uninstall Apache to free port 80, used by pi-hole web server (lighttpd); Adjust the Apache config to run the web interface correctly or use different ports for Apache and lighttpd. Did even another re-install of my complete setup, but it occurs again. The VM runs on the latest version of Proxmox. 1 Web Interface Version v1. I thought i would be nice to him and clicked on Settings -> restart systems. See "systemctl status lighttpd. Yet I am seeing my work laptop in the blocked logged. 0. 10). service: Scheduled restartt 5. piHole completely stops working. It is interfering with lighttpd (the Pi-hole web admin GUI webserver) and causing your problem. Reload to refresh your session. 2 to run pihole. failed!" I tried restarting. Also try a different browser to make sure the issue doesn't come from your Pi-hole. I have removed pihole and reinstalled after numerous boots. I trie to cat the FTL log file and this is the result : cat /var/log/pihole-FTL. It appears to only be an issue with the webserver part, and started after the unix update. net. 14. Pi-hole v5. check if all clients use the pihole als their dns. I also restarted the Raspberry Pi on which Pi-hole is installed. g: [X]} I have read and understood the contributors guide. My OS is Debian Stretch with Armbian Linux Pi-hole web interface not accessible after update #3745. We use optional cookies, as detailed in our cookie Sep 04 13:40:12 union-pi-hole-2 systemd[1]: lighttpd. However a couple of weeks ago I noticed that the web-interface was not working. Reading the docs, seems like if I remove this variable, Pi-hole will use default values unless the setting was set in the web interface. I followed the insctructions on Lighttpd does not start - #11 by djcraysey but this didn't solved the problem. Rest assured that this is not an issue, however, we will get it fixed. I configured cluster and tested it, all work like a charm. When this happens, I can still ping the device, but I cannot reach web interface or SSH. Please Since yesterday after restarting, I cannot connect to the Web Interface. Expected Behaviour: System should just continue to work normally, forever, without the need for a reboot. I do have unbound and wireguard running on the same Pi, but they have been running concurrently for a while with no problem. For both the Command-line Interface (CLI) and Web Interface, we achieve this through the pihole command (this helps minimize code duplication, and allows I'm trying to get pihole working, more for the nice logging and web interface than the blocking. This used to work until about 2 weeks ago. I've checked netstat and it shows lighttpd listening on port 80. Neither the webinterface nor the DNS Server is reachable from inside the Wireguard Network. Attempting to install unbound using this guide I get stuck in the Test validation step, where both commands return a SERVFAIL. https://tricorder. Nov 29 00:04:08 bpi-m2z systemd[1]: lighttpd. After the installation the web interface was accessible. Well i got it to update but then the DNS service would just stop after starting it manually every time. lighttpd refuses to start, blocking and dns over http works Debug Expected Behavior: Following this guide to install pihole: OS: Ubuntu 22. Look under "Advanced DNS settings" in the web interface and choose the "Listen on all interfaces, permit all origins" option under "Interface listening behavior". 2, and Web 4. conf will go back to pointing to the PiHole We want information information information. Sadly, that doesn't fix it. I tried to update it to the latest version and it failed a few times before i tried to get it repaired and working. clients. Restart does not work It wouldn't allow logging in with the password. One runs fine, the other errors 503 randomly. Android says "no internet connection" but the Pihole web interface is working fine DL6ER March 10, 2017, 1:01pm 5. Apache2 subdomain doesn't load content (mirrors main domain) 1. Pihole works fine on apache. Sep 04 13:40:12 union-pi-hole-2 systemd[1]: lighttpd. 1, FTL v4. The pihole is completely unresponsive - cannot SSH in, cannot use the web Since running a pihole -up followed by an apt dist-update, I am no longer able to access the admin web page. More precisely I get a "connection refused" if I want to connect to the web admin interface. After a few tries, I made it to the "Installation Complete!" message that includes the web interface address and default login password (I configured a static IP set to 192. In fact, I have configured it so that: http redirects to https (using Letsencrypt SSL certs) pihole is only accessible Expected Behaviour: I would like to be able to access the Pi-hole Admin-Web-Interface via a self signed SSL certificate. 4) AdminLTE version is v4. The core script of Pi-hole provides the ability to tie many DNS related functions into a simple and user-friendly management system, so that one may easily block unwanted content such as advertisements. x range. hole/admin or the ip. x ships with the web server lighttpd but this one seems to be failing. I've created two debug logs; one straight after rebooting the Pi, and another after then running pihole restartdns. At least we found 2 other ways to get PiHole working after reboot. i have a Minecraft server running Debian 10 buster, decided to set up Pi-hole on it because its compatible with Debian, it was super easy to set up, no problems there. Pi-hole works without problems, I can make and save changes in the web interface, I can see the logs, update the ad lists, etc. After I restart of my tinkerboard with pihole there is no internet access for my computer neither my cell phone or my tablet. Unfortunately, I cannot pinpoint the exact moment of change. I attach some screenshots here and hope, someone could help me. I have not yet set up any user for VPN. Scroll down and you'll see a few options, including "power off system" and "restart system". 4-LTS and all updates. myname. Expected Behaviour: to be able to open the Web GUI on port 80 Actual Behaviour: I get connection refused after every reboot. so long story short. I can reboot, mess with it a bit and get the admin interface to Removal PR here: Remove configureFirewall function, the call to it, and related tests by PromoFaux · Pull Request #3283 · pi-hole/pi-hole · GitHub Discussion here: basic-install. After a reboot not anymore. They were working perfectly fine before, and oddly, my computer that's connected by ethernet seems to be still getting DNS. I updated through PUTTY using the update command, and upon rebooting, none of my wireless networks are working and they cannot connect to the Internet at all. I've done a repair but no change. Changing the listen on buttons on the web interface will dynamically change interface lines, or remove them completely. If I try to use my Raspberry as DNS directly with my PC, I can't reach any websites anymore. Hi, my pihole was working until i realized today i can't access the web interface, but DNS query still working correctly. The issue I am facing: Since 2 days - on every reboot I am getting the following error: 2021-04-18 17:39:00 DNSMASQ_CONFIG FTL failed to start due to unknown interface eth0 Details about my system: Raspberry Pi 4 running ubuntu 20. That may imply that you had not restarted your Docker Pi-hole, or that Docker did not yield the ports upon a simple container restart, requiring removing the existing container before starting a fresh instance. When I check under the web interface - settings - it says FTL service is offline! . I would need help as my friend google can not help me anymore Expected Behaviour: Access to web interface Actual Behaviour: after a power outage the web interface is not accessible anymore. google. Actual Behaviour: The last 5 days i cannot access the web interface with pi. :white_check_mark: Router DHCP So I never get any status for "completed installation" and not possible to access pi-hole web interface or do anything for iproute2 [ ] Checking for whiptail SELinux not detected Using interface: eth0 Using upstream DNS: Quad9 (unfiltered, no DNSSEC) (9. sh: Allow dhcpd traffic in firewall-cmd by flavio-fernandes · Pull Request #3092 · If you have other web applications that you want to access from WAN, to not expose the Pi-hole admin panel, you can either enable ULAs and use them for the pi. After the Update it just stopped working. Your dig via 1. So I enabled the Pihole DHCP server. 0 The web interface does not work. Smiley85 August 16, 2017, Reboot the roku and see if your channel still works. For some reason the setting "Listen on all interfaces" is randomly not working properly with PiVPN for me. After entering the dns of the raspberry pi on which the pi-hole is placed into the router settings, the web interface of the pi-hole stopped booting. After I restart my machine (every time) Pihole stops working . Steps to Expected Behaviour: I'm running Pihole on a Raspberry Pi 4B. e. Recently pihole started not accepting my usual password and I have to ssh into the container to change it. I encounter the same issue every few days. Please see the logs below: Environment information: Host system is OpenMediaVault 6. Hello everyone, I am experiencing a problem with reaching the web interface of my pi-hole via the pi. I already tried running an fsck at boot, but I don’t have a monitor attached to the Pi. I reinstalled with the command pihole -r but to no avail. 0 containers Core v4. During installation I did NOT install lighttpd. A fresh install of Raspbian 64bit using Raspberry Pi Imager and installing pihole worked perfectly and as intended. Both networks are home networks and low traffic. 30-1 (Shaitan) based on Debian 11. 20. Reply reply [deleted] • I used to do that but WireGuard and Pi-Hole have a delay issue. If you are frustrated after hours of research and trying many solutions but did not work, a reboot usually helps. Actual Behavior Possible Fix Steps to Reproduce and debugging done. Both were built for, and run on, a Raspberry Pi 4 2GB using the same RasPiOS Bullseye "base" image. The only way i get it to work again is to use pihole -r to reconfigure everything. then check brwoser, cache, dhcp leases, reboot client, Summary: My PiHole is working intermittently, it is difficult to connect to it (SSH or WebAdmin), and any connections don't last long. Current: Pihole: 5. I stepped through the two configuration options but the end result did not change. If it fails, put that one back in the white list (I do whitelist editing via the pihole web interface btw). The last message is simply saying the server was stopped a few minutes after starting: We often see users with broken Web interfaces after updating Pi-hole but it has also appeared during regular usage. MPeti1 opened this issue Sep 9, 2020 · 3 comments Comments. On boot, that device has to connect to the network, at which point Pi-hole can operate. New replies are no longer allowed. Hello. g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category. Nov 16 08:52:47 pihole systemd[1]: lighttpd. (I made Thanks. Apache is an unsupported web server for Pi-hole, but users have solutions for making it work. sudo service lighttpd restart Job for lighttpd. In raising this issue, I confirm the following: {please fill the checkboxes, e. Also, press CTRL + SHIFT + R to reload the web interface from scratch, without using any cached files. I always need to install pi-hole again to get it working. The "total queries over last 24 hours" graph shows no queries, and the DHCP stops working; mobile devices drop off the wifi. If I roll back to image: pihole/pihole:2022. Still a mystery. system Closed November 9, 2023, 12:40am 6. Actual Behaviour: Web interface shows no logging information, though if I do tail pihole. Pi-Hole continues to work, but web GUI is not working. 9. The IP says it’s taking too long to respond; the pi. When it happens, I log into the pi-hole web interface using the pi-hole IP, go into settings and restart the DNS resolver to fix the issue. 8 will let us know if the Pi-hole has internet connectivity, regardless if DNS works or not. Unable to access PiHole Admin Interface on a device PiHole isn't Please follow the below template, it will help us to help you! Expected Behaviour: Actual Behaviour: the pihole web interface is not showing any queries even though it is blocking contents just fine. I use Ubuntu on an Orange Pi PC. It is an iterative process. Eg Total queries (- clients) Q Ok, gave up on this, and just left it! everything except the GUI seemed to work! Now after the latest update (Pi-hole Version V2. Thank you Web Interface Stopped Working. It's been running pihole for a long time. Actual Behaviour: URLs are not resolved. 30. com in terminal. Open comment sort options For me reboot followed by logout of web interface and back in solved it /etc/resolv. All tutorials and guides show it working flawlessly and mine Pi-hole web interface not updating in CLI using pihole -up Share Sort by: Best. SOLVED EDIT : the 16gb SD card was full. Also, when depending only on pihole (and turning off DHCP on the router), I have a lot of issues connecting to different webpages, mostly DNS errors. docker exec -it pihole /bin/bash sudo pihole -a -p The problem is that password change does not seem to persist and once I restart the container or stack, I have to reset the password again. Hey, configured my Pi-hole as I wanted, however when I restarted the server to connect it to UPS my WEB interface stopped working. the log files are empty in /var/log Debug Token: Use netcat. The issue I am facing: I accidentally power cycled my router and my pihole at the same time and now I'm not getting DNS on my wifi network afterwards. This seems to trigger PiHole as well. But the Idea was good: Installing a program that contains lighttpd. 112. After a long time of pi-hole running without a problem, I had to restart my RPi and now I see pihole's web interface displays plain text headings only, like a template without actual info. I can't ping pi. 1 as well as the ping results for 1. For the X-Pi-hole: The Pi-hole Web interface is working! X-Frame-Options: DENY Set-Cookie: PHPSESSID=qoac529ee5179ukuqoj9mngei1; path=/ alexiscordova changed the title Admin Web Interface Not Loading (404) on New Installation Admin Web Interface Not Loading in Chrome May 4, 2018. Now, after a reboot I cannot access to web interface from any server: login to ssh its ok but from web interface (tested in many browser) always return connection refued. network doesn't work after adding second interface to netplan. The debug token is nswo9i8zbx. . In the few times I was able to connect, storage space was about 20% Every time I restart my container, pihole creates a random password and does not use the password in my compose file. hole/admin doesn't work and pi-hole admin interface should be available automatically after reboot. 1. 10) Static IP already configured Unable to find IPv6 ULA/GUA address The title of your post is " PiHole falls off network after reboot", but it appears that the problem is not with Pi-hole (software), but rather with the underlying OS or device. I installed Proxmox on 3 new server and all the procedure from the iso went ok. Jun 25 21:03:48 raspberrypi systemd[1]: lighttpd. in init. You signed out in another tab or window. FYI I do not have the pi-hole running on the primary IP of the ubuntu machine, it has its own virtual interface of Pi-hole was working but web interface was returning 503 errors all the time. Web admin is available following install or a pihole -r reconfiguration, but This is a bug in Pi-hole's generated lighttpd config See: https://github. Power is using an original pi power supply. The symptoms include: the Web interface has endless spinning indicators the Web interface looks distorted the query log is stuck on Processing none of the Web interface stats load The solution in most cases is to flush your Web browser's cache or service Any ideas why it is not working with " Listen on all interfaces" ? nanopi@nanopineoplus2:~$ pihole -v Pi-hole version is v4. chrome, cache, dhcp release/renew and rebooting the client. I ended up uninstalling and purging lighttpd and then do Hi , I just update to the 5. Reinstalled the whole thing Web admin does not resolve at static IP address after reboot following either initial install or pihole -r. You switched accounts on another tab or window. eu to the local ip-adress of my raspberry Hi Everyone! I'm having some trouble installing Pi-Hole as a docker container. I can’t access Pi-hole web interface, also SSH connection via PuTTy. Don't EVER open port 53 in your router to expose that to the world. Reply kodavn Please follow the below template, it will help us to help you! Expected Behaviour: I accidentally bumped a power strip and restarted my Pihole. 18. hole, result Hello, i guess i have the same problem or similar. But it only recieves WhatsApp, Twitter and some news app notifications. I had not updated my Pi-Hole in a few months, and I saw today that version 5. This topic was automatically closed 21 days after the last reply. g. Web Interface v5. I also shutdown the system and put the sd in a card reader so I could fsck it on another system. 10, 149. It was working for a few weeks before the update, including right before the update. The URL you provided opens the admin page for me here. hole matches its Expected Behaviour: after i reboot the the system, i can still use pi-hole. Thanks for the workaround! 7 Please follow the below template, it will help us to help you! Hi, thanks for being part of this great project. Copy link MPeti1 commented Sep 9, 2020. Even after that the status remains on "unknown". service: Failed with Actual Behaviour: The last 5 days i cannot access the web interface with pi. DNS blocking is working though Debug Token: https://tri Web Interface not Working . Is there something I did wrong in my compose file? version: "3" services: pihole: container_name: pihole image: pihole/pihole:latest # For DHCP it is I agree major version are proper release procedure for breaking changes but the benefit of keeping the version mirrored between upstream Pi-hole projects and docker-pi-hole's is it prevents confusion by users thinking Pi-hole is on v5 and having to keep a mapping of 5. conf still seems to Hi everyone, I updated my Pi this morning, and everything else seems to be working fine but Pi-hole has stopped blocking ads. jkbv hljkx aizqxb cjkmxvo fjjiq nvrikt njng yiwpt jtgqp ugdgja