Hard coded refs to pi.hole in Beta 5 Web UI

General Beta 5.0
1

Alongside my operational Pi-hole v4.x, I have set up a second RPi named pihole-5 in order to run Pi-hole Beta 5.

Problem with Beta 5.0:

Opening http://pihole-5 in Vivaldi (Chromium) results in:

pihole-5
pihole-51220×310 9.17 KB

Browser reports having requested the following resources:

type url
font http://pi.hole/admin/style/vendor/SourceSansPro/SourceSansPro-Regular.ttf
image http://pi.hole/admin/img/favicon.png
font http://pi.hole/admin/style/vendor/SourceSansPro/SourceSansPro-Regular.ttf
css http://pi.hole/pihole/blockingpage.css
doc http://pihole-5/

It would seem that Pi-hole's web UI contains some hard-coded references to pi.hole somewhere, which differs from the actual URL used.

EDIT: In contrast, access by IP results in correct display of 'Did you mean to go to the admin panel?', showing no refs to pi.hole
type url
font http://192.168.1.233/admin/style/vendor/SourceSansPro/SourceSansPro-Bold.ttf
font http://192.168.1.233/admin/style/vendor/SourceSansPro/SourceSansPro-Regular.ttf
image http://192.168.1.233/favicon.ico
font http://192.168.1.233/admin/style/vendor/SourceSansPro/SourceSansPro-Bold.ttf
font http://192.168.1.233/admin/style/vendor/SourceSansPro/SourceSansPro-Regular.ttf
image http://192.168.1.233/admin/img/logo.svg
css http://192.168.1.233/pihole/blockingpage.css
doc http://192.168.1.233/

So maybe it's not a hard-code issue, but rather an odd occurence of self blocking?
How could an IP be handled correctly, while a hostname wouldn't?

EDIT: I*ve been able to track this JavaScript issue down to a firewall setting, so not related to Pi-hole, while ref issue remains.

Thought that would be only a minor, but trying to open http://pihole-5/admin next results in a 'JavaScript is disabled' message though it is indeed enabled:

admin
admin1024×530 27 KB

2

both running at the same time?

/etc/pihole/local.list, should be different on both machines.

Try using the IP address (use the correct (pi) IP addresses) e.g.
IPv4 http://10.0.0.1/admin
IPv6 http://[2a02:1522:1234:5322:f838:44a4:7833:1234]/admin

but I see your point. If the workstation has cached the wrong IP (other pi) the web interface will go crazy....

3

Yes, I am not worried so much about getting this second Pi-hole to work properly (I solely set it up to assist with Pihole -g / List download / disappointing performance - #112 by Bucking_Horn).

I just think that a request to htpp://pihole-5 should not invoke requests to http://pi.hole. And this also seems to interfere with correct detection of Javascript.

4

The changes, as a result of this 3 day test session with the developers and others (thanks to all) have been merged into beta5 yesterday. so if you run pihole -up on a beta5 system, you'll enjoy much faster list processing. Unfortunately, many other beta5 improvements have not yet been applied.

5

I am fully aware of that, as well as your substantial contribution in proof-testing it - but let's keep this topic focused on my issue, please.

1 Like
6

This thread and pull request may have some history of interest.