ERR_CONNECTION_REFUSED when accessing http://serverip/admin/

Help
1

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:

[Upgraded to latest version of pihole several days ago and now it seems that the admin website is not accessible. It also seems like the pihole is not working properly. I am running a standard pihole build on latest master versions on Ubuntu 22.04]

Actual Behaviour:

[I am trying to access the admin page using multiple browsers with http://server_ip/admin/ which usually works but not since the upgrade. Further, when I set this as my network's sole DNS server nothing is getting resolved properly so it seems like the install went bad. When I ran the pihole -d I did notice it mentioned a few things: /etc/lighttpd/conf.d does not exist, [✗] Failed to resolve pl17167975.safestgatetocontent.com on eth0, [✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888. I don't see any other obvious things in the pihole -d output.]

Debug Token:

[https://tricorder.pi-hole.net/u56KzIQv]

3

Where is this Pi-hole instance hosted? Your ethernet address (eth0 - the interface for which Pi-hole is configured) is a public IP.

4

Yes that is correct.

5

Why is your Pi-hole open to the internet? This is known as an "open resolver".

6

It's not. It is locked up with iptables.

7

Who is using your Pi-hole?

8

Myself primaily from different locations.

10

You should be using a VPN to securely access your Pi-hole and prevent remote intrusion.

We offer several guides.

11

Thanks for the link. Did anything look out of sorts besides the external IP in the tricorder logs?

12

Check your rulesets, you probably locked yourself out of the VPS you are running Pi-hole on.

13

Also your lighttpd configuration seems off, these are paths that don't look correct.

   2023-01-21 05:39:55: (gw_backend.c.530) connect /tmp/pihole-php-fastcgi.socket-0: Connection refused
   2023-01-21 05:44:04: (gw_backend.c.530) connect /tmp/pihole-php-fastcgi.socket-0: Connection refused
   2023-01-21 06:03:47: (gw_backend.c.530) connect /tmp/pihole-php-fastcgi.socket-0: Connection refused
14

This was exactly the problem. My IP changed, my 'dynamic' dns updated it but the server was resolving my old IP and blocking me.

15

The only reason I didn't mention that is because it is from so long ago.

17

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