Javascript is disabled error on iPhone

Expected Behavior:

Navigating to the admin page on an iPhone should not display the "Javascript is Disabled" error message when javascript is enabled.

Actual Behaviour:

When I navigate to the admin page on my iPhone I get the following error message: "Javascript is Disabled. Javascript seems to be disabled. This will break some site features. To enable Javascript click here." Javascript is enabled on this device.

Debug Token:

b9nbcxe8nl

pihole -up
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date

[✓] Everything is up to date!

I have tried rebooting the pi, but I am still seeing this issue.

I have tried and cannot replicate this what version of safari are you using?

Are there any other apps you are running that could be blocking the JS ?

Thanks for your reply. This is an iPhone 8 running iOS 11.4.1 using Safari and it is not jailbroken. I tried my iPad mini running the same OS and I am getting the same error there as well. One device had a content blocker installed, the other didn't. Beyond that I'm not sure if any way to directly interact with safari on the iPhone. This was a pretty close to vanilla pihole installation that was upgraded from the previous version. The only changes have made were a few additional white listed sites and 1 or 2 additional block list. The pihole is also my dhcp server, I'm not sure if that makes a difference. Is there anything beyond wiping it and starting from scratch that I should try?

Using an iPhone 8 and iOS 11 on Safari (using BrowserStack), I can not reproduce this issue.

There must be something causing the JavaScript in the header.js file to not execute, but lets the rest of the code run. That header code hides the JavaScript warning.

I got around to doing a clean install of raspbian stretch, along with a clean install of pi hole. Well I was seeing the same error on all devices (iPhone, iPad, and Mac) -- bummer. I did some more digging in some old post on reddit and someone suggested clearing the browser cache. That did fix the problem. So hopefully if someone else comes across this post, it will be noted here as well.

Cheers.

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