When I have IPS on, grainger.com stops working. When I turn it on I get a white page like what php does when you forget to put a semicolon at the end of the line or miss closing a quote.
I rarely go to this site, but someone was sharing me this link in a discussion on a different technical forum.
https://www.grainger.com/product/Gasket-Sheet-12-in-x-12-in-810L79?gQT=1
It only works if I disable IPS. I’m using abuse.ch rules
At the beginning of your post you say
And at the end
I am presuming that you mean the second occurrence.
I also have abuse.ch selected on my production ipfire and i could access that page you provided.
Have you modified the selection of rules inside the abuse.ch ruleset? I am just using the default set.
I tried to add “Abuse.ch SSLBL Blacklist Rules” and after that I could access grainger.com. What clues do you see in the logs? For me PING grainger.com says 23.54.0.11
Its the most strangest thing.
I can ping them from the raspberry pi, but it displays a white screen. However if I go over to the other computer on the green network, which is a windows 11 computer, it displays.
If I use my phone (connected to blue) it works.
If I turn off ips, grainger.com works on the raspberry pi again.
when I open up the debug console of the browser while the raspberry pi is blocked, it shows this error. In both chromium and firefox.
kA0YTPjk?v=e692d59d-…b173b&t=770739753:1 WebGPU is experimental on this platform. See https://github.com/gpuweb/gpuweb/wiki/Implementation-Status#implementation-status
kA0YTPjk?v=e692d59d-…b173b&t=770739753:1 Failed to create WebGPU Context Provider
www.grainger.com/:1 [GroupMarkerNotSet(crbug.com/242999)!:A0C054003C000000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader flag to opt in to lower security guarantees for trusted content.
www.grainger.com/:1 [GroupMarkerNotSet(crbug.com/242999)!:A03054003C000000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader flag to opt in to lower security guarantees for trusted content.
So its not necessarily IPS fault, however, its the combination of the two.
Its like its altering something like type encoding.
Since this is web site related to one platform type, I’m going to rule out that there is nothing wrong with IPS, however, it could be a side effect of font-config broken that I am going to look at thoroughly this week.
From your error messages it looks like you have WebGPU enabled in your browsers. Certainly in Firefox, this is labelled as experimental.
With your RPi, which does not have a GPU then I would presume that is why you get the message
The next two messages say that
Howwever deprecation does not mean you can’t use it, just that you should change because eventually it will be removed.
To be honest those messages may be occurring, but they don’t look like hard error messages.
However a simplest first step would be to disable the WebGPU in your browsers and see if the website still has problems.
Today it is behaving differently, but I updated the pi5 last night before going to sleep and now firefox works in both IPS conditions, but chromium doesn’t in both conditions.
When I go into about:flags in chromium the webGPU and webGL are disabled. When I enable it the site still doesn’t work.
I’m convinced this is a raspberry pi issue because youtube has problems in chromium and not in firefox and updating last night changed the behaviour I originally observed.