Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Open

Spurious "Warning: Potential Security Risk Ahead" error page with no way to proceed

jbr replied
tilmanschmidt

I am trying to access my QNAP NAS configuration page within my home LAN from a newly installed Linux PC with Firefox 147.0.1. Firefox won't let me access the page, popping up an error page:

Warning: Potential Security Risk Ahead

Firefox detected a potential security threat and did not continue to nessy.fritz.box. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.

I have verified that the claimed risk is nonexistant, but Firefox does not allow me to bypass the warning. There is no "Proceed anyway" or "Advanced..." button as claimed in various help articles.

How can I convince Firefox that I know what I am doing?

NB: The same page is accessible, also with Firefox 147.0.1, from a Windows PC.

I am trying to access my QNAP NAS configuration page within my home LAN from a newly installed Linux PC with Firefox 147.0.1. Firefox won't let me access the page, popping up an error page: Warning: Potential Security Risk Ahead Firefox detected a potential security threat and did not continue to nessy.fritz.box. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details. I have verified that the claimed risk is nonexistant, but Firefox does not allow me to bypass the warning. There is no "Proceed anyway" or "Advanced..." button as claimed in various help articles. How can I convince Firefox that I know what I am doing? NB: The same page is accessible, also with Firefox 147.0.1, from a Windows PC.

All Replies (2)

Nevermind. I switched to Epiphany. That works as it should: warned me once that the NAS uses a self-signed certificate, allowed me to accept it. No more bullshit about HTTPS with a self-signed certificate being more dangerous than unencrypted HTTP.

It depends on what the actual error code is. (Self-signed is not a problem, but you might have e.g. a recycled serial in the exclusions already or something like that, which isn't recoverable for the engine.)

Error screens got an overhaul recently so you might get different results on 152 and later.

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.