You're not, at this point, using https-only mode according to comment 0 and comment 3 so this is problem back to a "networking" problem than "DOM: Security". The https-only error page has a "Continue to HTTP site" button, not a "Try Again" button. Does your laptop also have AVAST installed? The AVAST product usually installs a MITM to inspect traffic and it's possible that's not playing well with Firefox. This is an option in AVAST that can be turned off if you dig through settings. Probably worth testing turning that off, or turning off AVAST entirely, and seeing if the problem goes away. If that fixes it we know to focus on a configuration problem (either AVAST, or Firefox proxy/cert settings). If it doesn't fix it we'll need to keep looking for other reasons. Could it be something interfering with DOH or HTTP/3, with the reload triggering a fall-back?
Bug 1730588 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
You're not, at this point, using https-only mode according to comment 0 and comment 3 so this is back to a "networking" problem than "DOM: Security". The https-only error page has a "Continue to HTTP site" button, not a "Try Again" button. That's a feature of the general Network Error page. Does your laptop also have AVAST installed? The AVAST product usually installs a MITM to inspect traffic and it's possible that's not playing well with Firefox. This is an option in AVAST that can be turned off if you dig through settings. Probably worth testing turning that off, or turning off AVAST entirely, and seeing if the problem goes away. If that fixes it we know to focus on a configuration problem (either AVAST, or Firefox proxy/cert settings). If it doesn't fix it we'll need to keep looking for other reasons. Could it be something interfering with DOH or HTTP/3, with the reload triggering a fall-back?