pihole-FTL and lighttpd services don't start in chroot environment

Expected Behaviour:

Admin interface should display stats and FTL should be online

Actual Behaviour:

  • FTL offline and admin interface displays "Lost connection to API"
  • I ran sudo service lighttpd restart so the admin interface was finally reachable. I also ran sudo service pihole-FTL restart but the admin interface still displays "FTL offline"
  • Pihole is installed on a Ubuntu 18.04 environment running on an android phone using Linux Deploy app

Debug Token:

https://tricorder.pi-hole.net/3us3l6mcie

This isn't a supported platform.

Interesting. Can you share more info on what makes this an unsupported platform? Specifically what's missing from Ubuntu 18 running in chroot environment compared to native Ubuntu 18.

A networking stack. An init system.

None of the developers would run it so we won't support it.

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the dummy0 interface.

[✓] IPv6 address(es) bound to the dummy0 interface:
   fe80::7881:80ff:fed7:2276 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)

   ^ Please note that you may have more than one IP address listed.
   As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.

   The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] li.livingsocial.com is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve li.livingsocial.com via Pi-hole (192.168.1.16)
[✓] doubleclick.com is 172.217.14.206 via a remote, public DNS server (8.8.8.8)

Missing init system.

*** [ DIAGNOSING ]: Pi-hole processes
[✗] lighttpd daemon is 
[✗] pihole-FTL daemon is 

Can you tell me more about what part of networking stack is missing. I can try debugging to see if I can make it work.

For the init stack, the Linux Deploy app allows using an init system (run-parts or sysv). Here are the screenshots from the app. Can I add a script here to make this work?

I can't but maybe someone else from the community will.

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