Strange error and FTL not working on every reboot

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.04 with NGINX for serving multiple sub-domains

What I have changed since installing Pi-hole:
I am just updating the standard ubuntu packages as well as the pihole. currently I am on:
Pi-hole v5.3.1 Web Interface v5.5 FTL v5.8

The error is correctable after I run the following command:
systemctl restart pihole-FTL.service

Either you don't have an eth0 or it's not UP/UP when pihole-FTL is started.

Solutions are to either use the correct interface name, might be something like enps0... or delay the startup of pihole-FTL with Configuration - Pi-hole documentation

Thank you for the quick and explanatory answer! Indeed a delay in starting up the pihole-FTL will help - I already applied such workaround using crontab:

@reboot sleep 10 && systemctl restart pihole-FTL.service

Thank you for pointing out the logical way of doing it. The eth0 is correct - I do have such interface, but apparently it is starting a bit later due to some ubuntu updates - this is the only reason I can think of, as my configuration runs unchanged for almost a year now without any issues.
Or there is a missing dependency for pihole-FTL.service :slight_smile:

Thank you one more time !

DELAY_STARTUP=5 was enough to cure it :slight_smile:

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