pidof pihole-FTL
returns a number, in this case 764.
Debug token is fbqa19c4t5.
How about:
sudo -u www-data pidof pihole-FTL
That returns nothing.
After entering the password, it returns the process number (764).
Check the output of these commands:
which pihole-FTL
sudo -u pihole which pihole-FTL
Both commands return the following:
/usr/bin/pihole-FTLAlso check these outputs (forgot to include the www-data commands)
sudo -u www-data which pihole-FTL
sudo -u www-data pidof pihole-FTL
Both commands return no output.
Thanks for the help in figuring this out, by the way -- this is a weird problem.
Hi, sorry for not responding quickly. Try another debug token. I think perhaps your web server might be improperly configured?
My new debug token is kq4p06lpgv.
About the web server -- there was no web server on this server before pihole installed one, so what would it have not properly configured, if there was no problems in the install log?
The debug log still looks good. I was wondering if the web server somehow setup a different user than what we expect (www-data). @DL6ER any ideas?
Have you tried doing a fresh install of the OS on the device?
Even better; I did a fresh install of pihole on a fresh install of a new Ubuntu 16.04 vm. Same result; web ui says no connection to api.
Run pihole -d for a debug token on that new VM
Will do -- just got back from a vacation, and will give it a try now.
Funny story: I tried installing it onto a fresh VM again, just to see what would happen, and it's working now. What did I do different?
This time I used Ubuntu Server 16.04, instead of Ubuntu Mini 16.04. I don't know what's different between the two in the end, since pihole should install all the packages it needs, right?
Either way, pi-hole is working great now on my Ubuntu Server VM install.
Okay, so it seems to be an issue of the Mini version of Ubuntu? I'm just preparing a virtual machine for it...
Yep -- just the mini version of Ubuntu. No problems running pi-hole on Ubuntu Server.
