Can't access web interface after pihole install

[jafeu]

Expected Behavior:

Following this guide to install pihole:

The World’s Greatest Pi-hole (and Unbound) Tutorial 2023 | Crosstalk Solutions

OS: Ubuntu 22.04.2 LTS

Hardware: Specification and hardware description of the Wyse 5070 (N11D) Thin Client
8GB Ram
Intel Celeron J4105 (Quad Core)
1.5GHz, up to 2.5GHz burst
No extra storage so I think I have the 30GB soldered eMMC

Actual Behavior:
Cannot access the web interface after initial pihole install and setup

Debug Token:
Rp5UysBB

Thank you for your help and time! No serious urgency with this as I will be out and about this weekend.

[rdwebdesign]

@jafeu

Cannot access the web interface after initial pihole install and setup

The web interface is working:

*** [ DIAGNOSING ]: Dashboard headers
[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!

Which address exactly are you using to access the web interface?

[jafeu]

I am using http://192.168.50.203/admin

[rdwebdesign]

The address looks correct and the debug log shows the web interface is working.

Did you try to access the web interface using a different device?

[jafeu]

I did. Tried it on the Ubuntu machine, my personal computer running windows, both of which are wired. Then I tried on my cell phone's browser.

It gets the furthest on my cell. It will warn that the site isn't secure and then when I click proceed, it gets stuck loading while still showing that warning message.

[chrislph]

Are these all using the Brave browser? It has a couple of features that bounce http over to https and they may be interfering. To test this you can try to disable it (or try a different browser to see if it behaves differently).

Apparently there are the two places in Brave where this is controlled [ the following is adapted from a forum post ] :

1. HTTPS Everywhere: This is based on a list of rules, and since you won't have added one for your Pi-hole this shouldn't be the cause here. Also, it’s covered by the Upgrade connections to HTTPS toggle in the Shields settings.
2. “HTTPS only” mode: This upgrades all HTTP URLs to HTTPS, no rules required. This is controlled by the Always use secure connections toggle in the Security settings. This would be the one messing with your Pi-hole connection.

[jafeu]

I have tried Brave, Edge, and Chrome.
The HTTPS only mode is not enabled on any of the browsers.

I just tried mozilla on the ubuntu machine and I can now get to the login/admin page. Will try again on my main machine after I clear and restore settings within the browsers.

[jafeu]

Still no go on my main machine when trying to use Edge, Chrome, or Brave.

Edit: Just installed mozilla on my machine - still no go

[Bucking_Horn]

@jafeu

• 192.186.50.203 took to long to respond
• Checking the proxy and the firewall

As that browser message already suggests, time-out issues often may hint at a firewall issue.

On the machine hosting your Pi-hole, check its firewall for Pi-hole's required ports, specifically port 80.

[jafeu]

Surely.

What would be the command to ensure port 80 is listening and is being listened by the server?

[jafeu]

Alright, so I google-fu'd it up. Found that only port 22 was open and listening using the ufw status command.
Went ahead and allowed http.

At this point I can access the web interface from my main pc. Ty for all the help!

Not sure why this didn't set in the first place. Any thoughts or insight on that would be appreciated.

[deHakkelaar]

@jafeu

Not sure why this didn't set in the first place. Any thoughts or insight on that would be appreciated.

UFW is not part of the Pi-hole install.
As there are many firewall tools available besides UFW for the many different Linux distros Pi-hole supports, Pi-hole cant account for all of them.
There is no normal software that I use and know of whom would alter the firewall.
You always have to read the prerequisites/requirements in the docs for the particular software.

EDIT:

@jafeu

Found that only port 22 was open and listening using the ufw status command.
Went ahead and allowed http.

Shouldnt you allow 53 TCP/UDP for DNS as well?

[jafeu]

So are you saying because I'm using Ubuntu, that it's normal for me to have to open that port?

I am new and admit that I just followed a guide that isn't necessarily made to install pinhole on a Ubuntu os..

Seems as though I will have to open 53 as well xD

[deHakkelaar]

@jafeu

So are you saying because I'm using Ubuntu, that it's normal for me to have to open that port?

Yes.
But there are a few Linux distro that dont have a firewall up OOTB.
Like for example Raspbian for my Raspberry Pi or other SBC distros like Armbian or TinkerOS.

Plus you have to consider that most distro releases come with a Linux kernel thats got all the firewall attributes already compiled into it or as a module:

pi@ph5b:~ $ lsmod
Module                  Size  Used by
[..]
nf_tables             200704  0
[..]
ip_tables              28672  0
x_tables               32768  1 ip_tables
[..]

nftables

nftables wiki