I ran Pi-Hole for about a month on a Raspberry Pi and it worked quite well. I've shut down the Raspberry Pi and set up a desktop running Ubuntu 16.04 Desktop and having problems. After running the install command everything seems to work fine but over the course of the day I've noticed that sometimes it works, and sometimes it doesn't. After rebooting the machine it usually won't work right off but an hour or two later it seems to be working again. It may work for a few minutes or several hours.
Is there anything special about setting up Pi-Hole on Ubuntu 16.04?
It looks like you set up Pi-hole to use the network interface eno1, but now that interface doesn't exist. Run pihole -r and choose Reconfigure to change it to a valid interface.
I reconfigured and it worked fine. The reconfigure listed eno1 as the only option. I selected it and it then worked. Then I rebooted and it no longer worked. I reconfigured it again and again it listed eno1 as the only option, which I selected. Then it worked again. I ran the debug again with it working, here is the token, ef4urbxsho .
I found mention in another forum of someone having a similar problem on another version of Linux. The responses indicated that on boot up his problem application was attempting to attach to the eno1 interface before that entity had been created in the boot up process. Could something similar be happening here?
Making changes to crontab made no difference. I even tried increasing the time to 60 seconds and then waiting a full two minutes after restart but it still wouldn't work.
I have found that after starting the computer and waiting until the GUI is finished loading I can enter "pihole enable" or "service dnsmasq restart" in terminal (both commands ask for my password) it will instantly start working after giving the password. Is there some way to automate this process?
I appreciate everyone's efforts to help me sort this out. I'm new to Ubuntu/Linux and still learning.
This is exactly what the command I showed you should do for use - wait some time and do the restart of dnsmasq. Are you sure you edited root's crontab (sudo crontab -e) and not your own (crontab -e)?
Otherwise, also try exchanging service dnsmasq restart by pihole enable.
I checked to make sure I was editing the proper crontab (sudo crontab -e) and found that the changes are indeed there. The file that sudo crontab -e edits is var/spool/crontabs/root. The changes are being saved there. I tried using pihole enable rather than service dnsmasq restart but it didn't work either.
Have look at How to run a command at login? - Ask Ubuntu to see how you would couple it with your login. You can specify in the sudo configuration that executing pihole doesn't need a password.
Making changes to the ~/.profile did try to start pihole but I could never get the sudo configuration to not ask for a password. I even tried editing the /etc/sudoers.d/pihole file that sets it to not ask for a password when starting the browser with no luck. For now I'm just going to shut Pi-Hole down. This is too much work just to get a simple program to run at start up. I'll come back to it later when I have time and have learned more about making Ubuntu do what I want it to do.
That is the exact line I entered into the very file you reference, but it still gave me an error when I rebooted. I'll get back to it eventually. I just have too many project going at the moment to deal with it right now. Thanks for the help!
