Fresh install on Synology using docker, zero queries and FTL cannot connect sometimes

Fresh install using docker and the steps at How to Install Pi-Hole on Your Synology NAS – Marius Hosting
Docker version 20.10.3-1308
Synology 1621+ with DSM 7.1-42661 Update 4
Router Unifi UDM Pro. WAN has been changed to the DNS of the Synology NAS on my network. No ports were entered in the DNS field.
IPv6 turned off at router level.

Actual Behaviour:

Dashboard showing zero queries or activity.

from log
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable

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

Debug Token:

Your debug token is: https://tricorder.pi-hole.net/WG6znW34/

Your debug log shows your system is using eth0 with IP 169.254.71.63:

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
    169.254.71.63/16

[✗] No IPv6 address(es) found on the eth0 interface.

This indicates you have no internet connection (dead linkdown):

*** [ DIAGNOSING ]: Network routing table
...
   169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.71.63 dead linkdown 
   169.254.0.0/16 dev eth1 proto kernel scope link src 169.254.11.59 dead linkdown 
   169.254.0.0/16 dev eth2 proto kernel scope link src 169.254.30.75 dead linkdown 
...

Looks like your machine doesn't have full internet access.

That's odd. I'm playing video games and browsing the internet from the same machine right now.
Hosting a plex server from my NAS and able to view files and download a new file.

Not sure why it's showing no connection I'm using the internet on every device.

I made a few changes router side, opened some ports, changed my DNS.

I'm getting a couple of hits on my pi-hole now. I think it's fixed.
Your debug token is: https://tricorder.pi-hole.net/BvjrR6HM/

Oh, sorry. I missed the other interface:

192.168.1.0/24 dev eth3 proto kernel scope link src 192.168.1.66 

I'm getting a couple of hits on my pi-hole now. I think it's fixed.

Good to know it's fixed.
If you are still seeing problems, you can post the command or compose file used to start your container.

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