No Web UI about addon-pi-hole

[frenck]

@mpgoebel Have you tried http://<ip of your device running hassio>/admin/index.php ?

The logs look fine though....

[mpgoebel]

I did try it both with my local ip and my external duckdns ip with both http and https, https shows error 404, http just timed out

[frenck]

Ok, that is odd, since 404's should not be served. It there something else serving maybe?

Some options:

• Try changing the web port to something different and try accessing it on the internal IP address.
• You are running a generic Linux installation of Hass.io. Ensure the correct interface is selected by the add-on (see debug information) or try to set it manually in the add-on configuration.

[mpgoebel]

I changed the web port to 85 and it worked on my internal ip but not my external IP, also it looks like the open web UI button only opens in port 80 instead of what was specified in the web port code. Also the interface is running on eth0

[mpgoebel]

Two things, I found that the let's encrypt add on occupies port 80 and I forwarded port 85 on my router but i get a"failed host check (external IP vs internal ip) when trying to access the web UI with my external IP:85.

[frenck]

@mpgoebel The failed host check is related to #6.
The working of the WebUI button is confirmed, but the issue is unsolvable due to a limitation of Hass.io. Port numbers for add-ons running on a host network level can't be picked up by the UI.

[mpgoebel]

The update fixed the open UI issue but i still am not able to see it as an iframe in the frontend

[frenck]

That is probably releated to #10, which will be fixed soon.

[mpgoebel]

Only other thing I saw that is odd is that I have not blocked any ads whatsoever since installing pi hole. Just lucky or is something setup incorrectly?

[frenck]

Did you point your devices to it? Does it actually filter?

[mdopp]

@mpgoebel Did it ever work with your router and port 80? Which router do you use? I used to have problems with my FritzBox, as it was not forwarding port 80, even if it was configured.

[mpgoebel]

@frenck I'm not sure how to point devices or which devices to point it at. It shows it has blacklisted sites but I don't think it has filtered anything.

[mpgoebel]

@mdopp I have forwarding setup for port 80. I use a unifi security gateway and controller for my networking at home. I just have 80 to 80 on my Pi's address.

[frenck]

@mpgoebel This is one method:
https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245

[frenck]

This is becoming a support and/or chat issue.
I like to keep the GitHub project about true issues with the code base.

Could you guys please refer to the Home Assistant forum or chat for general support questions? That would be awesome.

[Makr91]

Try adding the domain you have your SSL for here: "ipv4_address": "pi.example.com",

[frenck]

Please ignore that advise of @Makr91. While it is a valid workaround, it will cause other issues in the long run. The issue at hand is current in issue #10 and will be fixed soon.

[frenck]

Locking down this issue. This is not a forum.