Nginx returns '502 bad gateway'

Expected Behaviour:

'pihole status' returns:
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled (OK)

'pihole -r' completes with no errors

Running under:
Debian 10.3
On BeagleBone Black
uname -a
Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l GNU/Linux

running on

Actual Behaviour:

attempting to load admin page returns:
'502 Bad Gateway nginx/1/14.2'

clients using pihole dhcp are unable to loafd webpages

Seems like it broke while trying to figure out how to get Debian to stop assining my old dhcp address to my BBB. I fixed this by uninstalling connman. The BBB server is able to ping and name resolve internet hosts. Prior to this I also had issues with /etc/dnsmasq.d/SoftAp0 entry causing pihole to fail to start fully; this was solved by removing the offending entries and making the file immutable with 'chattr +i'

Debug Token:

https://tricorder.pi-hole.net/x3ibv4s9k3

Aha well it should not have nginx! I think nginx gets installed on BBB images so you can just plug it into USB, bridge the network, and then pull up a BeagleBone webpage which resides locally. Anyhow I have disabled nginx and at least that solves the '502' error and the admin page will load. Just have to figure out why 'FTL' status is 'offline"

SO BIG TAKEAWAY: If you use a BeagleBone Black with Debian, you must first disable the default nginx setup!

dnsmasq was somehow running again. I thought I disabled it, but perhaps just stopped it and then forgot once the nginx problems began. I've disabled it, and now everything is green.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.