Pi-hole web interface broken

Edulikesguiltygear · October 15, 2025, 2:24pm

Expected Behaviour:

Being able to access the web interface for pihole

Being able to upload the logs from pihole -d to tricorder.pi-hole.net

Operating System: Debian 13.1.0
Hardware: Positivo Mobile Z68

Actual Behaviour:

Web interface hangs up on “Transfering data to <pi-hole ip:80/admin>/<pi.hole/admin>“, and keeps loading forever. Which is pretty weird since it was working before i upgraded the security on my server (adding SElinux and changing how ssh works)

When attempting to upload the logs from pihole -d, it prints out one of the following: “curl: (22) The requested URL returned error: 502” or “curl: (16) Error in the HTTP2 framing layer”, the latter being more common.

Attempted fixes:

I upgraded my system and cleaned it afterwards, tried pihole -r and pihole -up, neither fixed it.

The web interface hang up has happened to me before and pihole -r fixed it. Dont know why its not fixing it this time.

Debug Token:

rdwebdesign · October 15, 2025, 3:44pm

The debug log doesn't show an issue with the web interface.

Something was changed on your network and the web interface can't be found.

The message "curl: (22) The requested URL returned error: 502" means "Bad Gateway". This usually happens when the server can't answer.

In conjunction with "curl: (16) Error in the HTTP2 framing layer" this could mean a network config issue.

Edulikesguiltygear · October 15, 2025, 5:11pm

Thank you for the reply! Im not sure how i should go about solving this issue, i forwarded a few ports on the same server im running pi-hole on, maybe that has to do with it.

Also, after a while of waiting, the web interface stops loading and its just the login screen but all jumbled up, like it hasnt finished loading yet.

The DNS works fine as well, its literally just these two errors.

Edulikesguiltygear · October 16, 2025, 9:58pm

After closing port 8080 and 4443 on my router and restarting it, pihole -d now works.

But the web interface still doesnt work. Here is the debug token:

I can also send a screenshot of how the web interface looks after “loading“, i just need to wait a bit.

rdwebdesign · October 16, 2025, 10:24pm

Not really sure why closing ports on your router would affect the debug log upload, but I'm glad it is now working (one issue was solved).

What do you see if you try to access the web interface using this URL: http://192.168.3.64/admin ?

Do you see any error messages?

Edulikesguiltygear · October 16, 2025, 10:43pm

This is what it shows.

But after a while of loading, it shows this:

Entering the password also leads to a loading hell.

The screenshot isnt showing it, but there is a little message at the corner of the screen saying “Transfering data from 192.168.x.xx/pi.hole“

Im also quite confused, maybe it was me restarting the router for a longer period of time. Just glad it was solved

Edulikesguiltygear · October 16, 2025, 11:52pm

This is how it looks like after inputing the password:

I tried inputting it again and its just the same page. Keep in mind that these pages take a while to load.

rdwebdesign · October 17, 2025, 12:17am

Looking at your screenshots I can see some CSS stylesheet files were not loaded. Maybe some javascript files are also missing.

Please answer these 2 questions:

Do you see any error messages on the browser console (devtools)?
are you using any browser extension? If you are, try again after disabling the extensions.

If you are still having the issues, try to access the web interface from a different machine or using a different browser. Does it fix the issue or do you see the same?

Edulikesguiltygear · October 17, 2025, 1:02am

Yes, and a lot of them. There are more warnings than errors on my main browser Librewolf, than on regular firefox and chrome. Im going to type some of the messages i receive here:
Librewolf:
Firefox:
Chrome is just “Failed to load resource“ 6 times

Yes, i disabled them and the issue still persist. Also it used to work before, in the same browser with the same configs.

I tried Librewolf and firefox in the same machine, safari on my phone, and chrome on a separate laptop, which all yielded the same results. Only the laptop doesnt use pihole dns.

rdwebdesign · October 17, 2025, 6:13am

None of these errors are related to Pi-hole.

Apparently they are related to some browser extensions related to search (SearchOneOffs, Region.sys.mjs, TopSitesFeed.sys.mjs).

Before what, exactly? Did you recently update your system?

Pi-hole was not updated since July.

I really don't know what is happening.

Edulikesguiltygear · October 17, 2025, 7:40pm

Before i updated my server, removed apparmor, installed SElinux, and forwarded some ports. Also my ISP doesnt let me configure my router manually, i have to contact them to forward/do something in my router, so maybe they changed something there.

Sorry if any of this is confusing, and thanks for the help!
(Also i cant send links to my logs for some reason)

rdwebdesign · October 17, 2025, 9:03pm

You probably added too many links in one post and the system flagged the message as spam.

If you want to post logs (specially when the logs contain links, e-mails, HTML tags, etc), please add the logs inside a code block using the "preformatted text" button </>.

The button will add lines with ´´´ before and after the code.
This is how it would look like:

code block containing

line breaks
  indented lines
  more indented lines
  HTML code <b>this won't be bold</b>.

and URLs that doesn't trigger
the "link" formatter, like this one: www.example.com

Edulikesguiltygear · October 17, 2025, 9:26pm

Ah, i see, thanks for the help!Here is what i was going to type originally:I completely removed any extensions from firefox and did 2 tests, one with the pi-hole dns, and one without it (i dont know if that affected it, but it did yield different logs):

NotFoundError: No such JSProcessActor 'BrowserToolboxDevToolsProcess'
Missing resource in locale en-GB: devtools/client/toolbox.ftl
Missing resource in locale en-CA: devtools/client/toolbox.ftl
1760717935005	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/95e747eb-3121-4b1d-889a-2e9706bdb11c/health/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760717935005	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 95e747eb-3121-4b1d-889a-2e9706bdb11c: {"isTrusted":true} Log.sys.mjs:722
1760717935005	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/0d3d3d4d-1aca-4d81-9562-380e5cf46c86/main/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760717935005	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 0d3d3d4d-1aca-4d81-9562-380e5cf46c86: {"isTrusted":true} Log.sys.mjs:722
1760717935006	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/c1f38de2-7f43-4bca-ab4e-96f510e62b3e/health/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760717935006	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping c1f38de2-7f43-4bca-ab4e-96f510e62b3e: {"isTrusted":true} Log.sys.mjs:722
1760717935006	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/2a5896f1-2ce7-453a-ba2e-779c9df8dd28/event/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760717935006	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 2a5896f1-2ce7-453a-ba2e-779c9df8dd28: {"isTrusted":true} Log.sys.mjs:722
1760717935006	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/8a2f24c2-3d62-4726-ae08-1c1357bbd546/health/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760717935006	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 8a2f24c2-3d62-4726-ae08-1c1357bbd546: {"isTrusted":true} Log.sys.mjs:722
1760717935006	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/5e4f01de-23d9-4655-a51e-5bffdc53925c/event/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760717935006	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 5e4f01de-23d9-4655-a51e-5bffdc53925c: {"isTrusted":true} Log.sys.mjs:722
1760717935006	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/8e7b7390-d380-43f0-8ed6-78700504333d/main/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760717935006	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 8e7b7390-d380-43f0-8ed6-78700504333d: {"isTrusted":true} Log.sys.mjs:722
1760717935007	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/6b9fa60e-01d3-4f85-95e5-ca737bd28bbf/main/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760717935007	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 6b9fa60e-01d3-4f85-95e5-ca737bd28bbf: {"isTrusted":true} Log.sys.mjs:722
1760717935007	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/730a3d94-b245-4abc-a871-6587197f2b14/event/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760717935007	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 730a3d94-b245-4abc-a871-6587197f2b14: {"isTrusted":true} Log.sys.mjs:722
1760717935007	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/4b68d60c-0a6f-4956-9a57-842aeba91ece/health/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760717935007	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 4b68d60c-0a6f-4956-9a57-842aeba91ece: {"isTrusted":true} Log.sys.mjs:722
TopSitesFeed: Failed to fetch data from MARS server: NetworkError when attempting to fetch resource. TopSitesFeed.sys.mjs:721
1760718895026	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/95e747eb-3121-4b1d-889a-2e9706bdb11c/health/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760718895026	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 95e747eb-3121-4b1d-889a-2e9706bdb11c: {"isTrusted":true} Log.sys.mjs:722
1760718895026	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/0d3d3d4d-1aca-4d81-9562-380e5cf46c86/main/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760718895026	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 0d3d3d4d-1aca-4d81-9562-380e5cf46c86: {"isTrusted":true} Log.sys.mjs:722
1760718895026	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/c1f38de2-7f43-4bca-ab4e-96f510e62b3e/health/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760718895026	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping c1f38de2-7f43-4bca-ab4e-96f510e62b3e: {"isTrusted":true} Log.sys.mjs:722
1760718895026	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/2a5896f1-2ce7-453a-ba2e-779c9df8dd28/event/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760718895026	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 2a5896f1-2ce7-453a-ba2e-779c9df8dd28: {"isTrusted":true} Log.sys.mjs:722
1760718895026	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/8a2f24c2-3d62-4726-ae08-1c1357bbd546/health/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760718895026	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 8a2f24c2-3d62-4726-ae08-1c1357bbd546: {"isTrusted":true} Log.sys.mjs:722
1760718895027	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/5e4f01de-23d9-4655-a51e-5bffdc53925c/event/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760718895027	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 5e4f01de-23d9-4655-a51e-5bffdc53925c: {"isTrusted":true} Log.sys.mjs:722
1760718895027	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/8e7b7390-d380-43f0-8ed6-78700504333d/main/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760718895027	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 8e7b7390-d380-43f0-8ed6-78700504333d: {"isTrusted":true} Log.sys.mjs:722
1760718895027	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/6b9fa60e-01d3-4f85-95e5-ca737bd28bbf/main/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760718895027	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 6b9fa60e-01d3-4f85-95e5-ca737bd28bbf: {"isTrusted":true} Log.sys.mjs:722
1760718895027	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/730a3d94-b245-4abc-a871-6587197f2b14/event/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760718895027	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 730a3d94-b245-4abc-a871-6587197f2b14: {"isTrusted":true} Log.sys.mjs:722
1760718895027	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/4b68d60c-0a6f-4956-9a57-842aeba91ece/health/Firefox/144.0/release/20251009125714?v=4: eUnreachable Log.sys.mjs:722
1760718895027	Toolkit.Telemetry	ERROR	TelemetrySend::sendPersistedPings - failed to send ping 4b68d60c-0a6f-4956-9a57-842aeba91ece: {"isTrusted":true}

NotFoundError: No such JSProcessActor 'BrowserToolboxDevToolsProcess'
Missing resource in locale en-GB: devtools/client/toolbox.ftl
Missing resource in locale en-CA: devtools/client/toolbox.ftl
LoginManagerPrompter: Couldn't process supplied URIString: http://192.168.3.64 4 LoginManagerPrompter.sys.mjs:929:16

system · November 7, 2025, 9:27pm

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