Website ing.be doesn't open in my FF
I'm unable to open the website https://ing.be/en/individuals Here are the error messages, when I try to open the site:
{"message":"invalid_request","uuid":"a147e7b1f2eb7aa8-000000002ada4ae6-000000006527e963"}
X-Firefox-Spdy: h2 cache-control: private, max-age=0, no-cache, no-store content-length: 513 content-type: application/json date: Thu, 12 Oct 2023 12:41:07 GMT expires: 0 pragma: no-cache strict-transport-security: max-age=31622400; includeSubDomains x-content-type-options: nosniff x-ing-response-id: de8efe166d3f11757404a2ed895a5e40 x-xss-protection: 1; mode=block
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8 Accept-Encoding: gzip, deflate, br Accept-Language: pl,en-US;q=0.7,en;q=0.3 Cache-Control: no-cache Connection: keep-alive DNT: 1 Host: www.ing.be Pragma: no-cache Sec-Fetch-Dest: document Sec-Fetch-Mode: navigate Sec-Fetch-Site: none Sec-Fetch-User: ?1 Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0
In other browsers and on my phone the website opens properly.
Solution eye eponami
OK, I have found the guilty extension: Disable HTML5 Autoplay. :) Many thanks again for your kind help!
Tanga eyano oyo ndenge esengeli 👍 0All Replies (5)
Try clear cookies and site data from the padlock icon in the address bar and do a hard refresh by holding down the Shift key while clicking the refresh button.
Many thanks for the tip. It partly solved my problem: the website now opens, but I'm unable to navigate on the page - there's a blue progress bar on top of the page that doesn't reach the end. When I copy the adress of the links that freezes (for example https://www.ing.be/en/individuals/saving) and paste it to the new tab - it opens. But not by navigating. When the site opens and I click the home button to go up, it freezes with the unfinished progress bar. I have disabled uBlock and HTML5 autoplay blocker for this website - no change.
It works for me. Does it still happen in Troubleshoot Mode?
In troubleshoot mode it works ok. How may I find the extension to blame for my problems?
Solution eye oponami
OK, I have found the guilty extension: Disable HTML5 Autoplay. :) Many thanks again for your kind help!