Expected Behaviour:
Able to access webui at /admin
Actual Behaviour:
ERR_CONNECTION_TIMED_OUT
Are you able to SSH into the device? Your debug token looks like it was made from the web interface.
Yes - I am using the Weblish console on my VPS to access the command line
looks like my dnsmasq service is failing to start. I recently upgraded ubuntu to 16.04
~# sudo systemctl status -l dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset:
Drop-In: /etc/systemd/system/dnsmasq.service.d
└─10-restart-failure.conf
/run/systemd/generator/dnsmasq.service.d
└─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
Active: activating (auto-restart) (Result: exit-code) since Mon 2019-07-08 01
Process: 11670 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=1/FA
Jul 08 01:11:38 ... systemd[1]: dnsmasq.service: Contr
Jul 08 01:11:39 ... systemd[1]: Failed to start dnsmas
Jul 08 01:11:39 ... systemd[1]: dnsmasq.service: Unit
Jul 08 01:11:39 ... systemd[1]: dnsmasq.service: Faile
Since Pi-Hole V4, dnsmasq does not run as a separate process; the code is embedded in pihole-FTL. You can check the status of pihole-FTL with:
sudo service pihole-FTL status
and verify which processes on running on ports used by Pi-Hole and other DNS software with:
sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:67 \|:80 \|:471'
thank you. any issues showing?
sudo service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; bad; vendor preset: enabled)
Active: active (exited) since Fri 2019-07-05 15:15:05 UTC; 2 days ago
Docs: man:systemd-sysv-generator(8)
Process: 10284 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUC
Process: 10330 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/S
Tasks: 0
Memory: 0B
CPU: 0
Proto Recv-Q Send-Q Local Address Foreign Address State e
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN L
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN L
tcp6 0 0 ::1:4711 :::* LISTEN L
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 :::53 :::* LISTEN L
udp 0 0 0.0.0.0:53 0.0.0.0:* L
udp6 0 0 :::53 :::* L
You cut off the right side of the output for the port command. It should look like this, with a PID/Program name column on the right.
The pihole-FTL status looks normal - running for 2 days, etc.
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 26428/pihole-FTL
tcp 0 0 127.0.0.1:5353 0.0.0.0:* LISTEN 30078/unbound
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 26255/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 26428/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 26428/pihole-FTL
Oops, sorry about that
sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 10400/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 19595/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 10400/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 10400/pihole-FTL
tcp6 0 0 :::80 :::* LISTEN 19595/lighttpd
tcp6 0 0 :::53 :::* LISTEN 10400/pihole-FTL
udp 0 0 0.0.0.0:53 0.0.0.0:* 10400/pihole-FTL
udp6 0 0 :::53 :::* 10400/pihole-FTL
Looks like everything is normal in these outputs. You original debug log is expired - please upload a new one and post the token here.
A few problems showing in your debug log:
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the wg0 interface:
10.192.122.1/24 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)
[✗] No IPv6 address(es) found on the wg0 interface.
[i] Default IPv4 gateway: 45.33.97.1
* Pinging 45.33.97.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
[i] Default IPv6 gateway: fe80::1
* Pinging fe80::1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.