reisender1967 gave kudos to itman in Banking & Payment protection not working after enabling new security feature of Mozilla Firefox v83.0
First, here's a write-up on the feature: https://www.askvg.com/tip-enable-https-only-mode-for-websites-in-mozilla-firefox/
Next, I enabled the feature in Firefox. There is no problem with accessing my bank's web site if I open B&PP via desktop icon. However if I try to access my bank's web site via a normal Firefox browser session, I get the same Eset help web page redirection as described.
Of note is B&PP uses a separate Firefox profile than the one used in normal Firefox mode. So I also set;
to true in that profile.
Still a no go as far as B&PP mode opening from regular browser mode. My suspicion is has something to do with the HTTPS always mode setting interfering with the initialization of Firefox protected B&PP mode.
Don't believe this be a quick fix by Eset. In any case, one can gain access to their banking web site with this HTTPS setting always on via B&PP desktop icon.
Personally I believe this HTTPS setting always on in Firefox is not needed since Eset scans all HTTP traffic the same way it scans HTTPS traffic; abet w/o MitM SSL/TLS protocol scanning mucking up things.
reisender1967 gave kudos to dom.piotr.85 in Banking & Payment protection not working after enabling new security feature of Mozilla Firefox v83.0
The latest version of Mozilla Firefox v83.0 has been equipped with a new feature consisting in enabling the mode of forced use of HTTPS protocol only, which can increase the security of browsing on the Internet. After enabling this security feature and visiting a banking website to make payments, the ESET Smart Security Premium Banking & Payment protection feature don't work any more. Protected browser window don't start. Instead, the ESET Help website titled 'How To Fix "Unable to Redirect Banking & Payment Protection to the requested website" error' is displayed.
By following to all the indicated repair steps, the error still persists. The only way, so far, is to not use the new Mozilla Firefox security feature and wait while you will fix new bug.