Behaviour:
I am trying to run pihole on ubuntu server 20.04 and I am unable to reach the pihole web interface to set it up. I am ssh to my raspbery pi 4, 4GB and retried the install multiple times.
Your debug log show several problems.
You have nginx running on port 80, which is preventing the Pi-hole web server (lighttpd) from binding on that port.
[80] is in use by nginx (https://docs.pi-hole.net/main/prerequisites/#ports)
*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 404 Not Found
Server: nginx/1.18.0 (Ubuntu)
Date: Mon, 01 Nov 2021 11:04:59 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Pi-hole is not configured for any active interfaces. You have no active IP on the ethernet interface, but that is what Pi-hole is configured to listen on. Run pihole -r and select reconfigure to correct this.
*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.
** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] stats.partypoker.com is 0.0.0.0 on lo (127.0.0.1)
[✓] No IPv4 address available on eth0
[✗] Failed to resolve stats.partypoker.com on wlan0 (192.168.0.69)
[✗] Failed to resolve stats.partypoker.com on docker0 (172.17.0.1)
[✓] doubleclick.com is 142.250.204.14 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 280 bytes from wlan0:192.168.0.1
*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.0.69/24
Your DHCP server (the router) is passing out its own IP for DNS, and should be passing out the IP of the Pi-hole.
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 280 bytes from wlan0:192.168.0.1
Offered IP address: 192.168.0.26
Server IP address: N/A
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.0.1
lease-time: 86400 ( 1d )
netmask: 255.255.255.0
router: 192.168.0.1
dns-server: 192.168.0.1
domain-name: "Home"
--- end of options ---
DHCP packets received on interface wlan0: 1
DHCP packets received on interface docker0: 0
DHCP packets received on interface lo: 0
DHCP packets received on interface eth0: 0
How do I run pihole on a different port?
I ran pihole -r, https://tricorder.pi-hole.net/NkCz1S0P/
and I am not sure what to do to fix my router settings, this is the LAN Page:
The issue isn't with pihole-FTL, which runs on port 53. The issue is with lighttpd, which is on port 80. You can either change the lighttpd port or the nginx port, or remove nginx completely.
A permanent way to change the lighttpd port is:
https://discourse.pi-hole.net/t/lighttpd-daemon-wont-start/44985/13
No file or image uploaded.
I can now access the web interface but it is still not blocking anything.
https://tricorder.pi-hole.net/dT8w5foD/
FYI I have Optus NBN
There does not seem to be an active DHCP server on your network:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
DHCP packets received on interface eth0: 0
DHCP packets received on interface docker0: 0
DHCP packets received on interface lo: 0
DHCP packets received on interface wlan0: 0
What does that mean?
When a client joins the network and is looking for an IP and DNS assignment, a DHCP server should answer and provide those things. In this case, no DHCP server answered.
If the clients do not have the IP of Pi-hole as DNS server (this is typically provided by the DHCP server), they won't use Pi-hole for DNS.
So is that a setting in my router?
I have tried manually setting my dns do my pi's ip4 address.
Also I am unable to set my primary dns server with my router.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.