Problem logging into my royalbank.com account
After upgrading to Firefox Ver 70 and newer I am having problems accessing my royalbank.com bank account. It looks like I can successfully log in, but once I am redirected to my account web page the screen goes blank. When I called royal bank they told me it is related to how Firefox's enhanced blocking protection is causing this. I have created an exemption to exclude royalbank.com and associated domains from these FireFox protections, but sadly this is not working. I have also confirmed that I can successfully access my royalbank.com account using Internet Explorer and Chrome and so definitely this is a Fire fox issue. Hopefully this issue will be elevated to the FireFox team so that it can be resolved in a further release.
Valgt løsning
There appears to be a problem with accessing some page on RBC websites where Firefox closes the connections to the server due to a server response that the server sends causing the pages to appear blank.
A possible workaround for now until this is fixed is to disable HTTP2 in Firefox by toggling this pref to false on the about:config page.
- network.http.spdy.enabled.http2 = false
- https://support.mozilla.org/en-US/kb/about-config-editor-firefox
Best is to create a new profile and disable HTTP2 in this profile.
See also my replies in [this thread]:
Læs dette svar i sammenhæng 👍 0Alle svar (2)
Valgt løsning
There appears to be a problem with accessing some page on RBC websites where Firefox closes the connections to the server due to a server response that the server sends causing the pages to appear blank.
A possible workaround for now until this is fixed is to disable HTTP2 in Firefox by toggling this pref to false on the about:config page.
- network.http.spdy.enabled.http2 = false
- https://support.mozilla.org/en-US/kb/about-config-editor-firefox
Best is to create a new profile and disable HTTP2 in this profile.
See also my replies in [this thread]:
Good day cor-el, Thank you very much for your post and the information! Indeed, your solution corrected the issue and so all is well! Thank you once again! Cheers, Sam