FTL troubleshooting

[shutyour]

Please follow the below template, it will help us to help you!

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

FTL is online

Actual Behaviour:

FTL failed to start due to failed to creat listening socket for port 53: Address already in use. I can't find in the logs what process is already using port 53

Debug Token:

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

[rdwebdesign]

Your log shows port 53 is in use by dnsmasq.

*** [ DIAGNOSING ]: Ports in use
(...)
[53] is in use by dnsmasq (https://docs.pi-hole.net/main/prerequisites/#ports)
[53] is in use by dnsmasq (https://docs.pi-hole.net/main/prerequisites/#ports)

You need to disable dnsmasq and then start FTL.

[shutyour]

Thanks not sure how I missed that.

[shutyour]

Also is FTL necessary for normal ad blocking, assuming disabling dnsmaq will also disable ad blocking?

[rdwebdesign]

The dnsmasq instance showing on your debug log is not related to Pi-hole and it needs to be disabled.

pihole-FTL (also called FTL) is part of Pi-hole and it is necessary.

[shutyour]

Thank you I also updated to latest version and all is well. FTL looks to be no longer a separate service on the dashboard.