PR_CONNECT_RESET_ERROR in Firefox: Causes & How to Fix It

What Is PR_CONNECT_RESET_ERROR?

PR_CONNECT_RESET_ERROR is an error code from Firefox. It appears on a page titled "Secure Connection Failed", which says the page "cannot be shown because the authenticity of the received data could not be verified" (Firefox). Since Firefox 151 (May 2026), the page adds: "What can you do about it? The issue is most likely with the website, and there is nothing you can do to resolve it."

Despite that wording, the problem usually isn't a bad certificate, and it's often not the website either. The code comes from NSPR, the networking library Firefox uses, and it means the connection was reset: while Firefox was setting up the secure connection, something sent a TCP reset (RST) and cut it off. Firefox shows the same generic text for every failure inside its secure-connection layer, so the line about authenticity doesn't describe what happened here.

It's the Firefox equivalent of Chrome's ERR_CONNECTION_RESET, and the causes are largely the same: software or a network device between you and the site is killing the connection.

What Causes PR_CONNECT_RESET_ERROR?

Fix 1: Find Out Whether It's Your Network

• Open the site on your phone using mobile data with Wi-Fi off. If it loads there, the reset comes from your computer or your network.
• Open it in Chrome or Edge on the same computer. If those show ERR_CONNECTION_RESET too, the cause is outside Firefox: antivirus, VPN, proxy or the network.
• Check the site from outside with DNS Robot's Port Checker on port 443 and the SSL Checker. If both connect for us, the site is up: the reset comes from your computer or network, or the site's firewall is blocking your address.

Fix 2: Pause Your Antivirus's HTTPS Filtering

Antivirus products decrypt HTTPS traffic to scan it, and when the scanner can't handle a site it may reset the connection, so Firefox reports PR_CONNECT_RESET_ERROR. The setting has different names: Enable SSL/TLS under Protections → SSL/TLS (ESET), Encrypted connections scan set to "Do not scan encrypted connections" (Kaspersky), Enable HTTPS scanning in Web Shield, called Web Guard in newer Avast (Avast and AVG), or Encrypted web scan (Bitdefender).

Turn off only that option, restart Firefox and reload. If the site works, add it to the product's exclusions, turn filtering back on, and update the antivirus.

Fix 3: Check Firefox's Proxy Setting

Firefox has its own proxy setting, separate from Windows and macOS. Open Settings, type proxy in the search box and click Configure proxy (in current Firefox it's under Privacy and security → Connection and software security → Advanced settings; Firefox 149 and older, including ESR 140, have it under General → Network Settings → Settings…). If you don't use a proxy on purpose, choose No proxy (or Use system proxy settings if your organisation sets one), click OK and reload.

If the computer is set to use a proxy, check the system setting too: on Windows 11, Settings → Network & internet → Proxy; on a Mac, System Settings → Network → your connection → Details… → Proxies.

Fix 4: Turn Off VPN and Check DNS over HTTPS

Disconnect any VPN completely and disable VPN or proxy add-ons in about:addons, then reload. If the site only fails on one network, the opposite can also work: a trusted VPN gets around a filter that resets connections to blocked sites, as long as using one is allowed there.

Firefox can also use DNS over HTTPS, and a filtering resolver can send you to an address that resets HTTPS connections. In Settings, search for DNS over HTTPS, open Advanced settings and switch it Off or back to Default (Default Protection in older versions), or choose a different provider, then reload. DNS over HTTPS also matters for filters that read the site's name from the start of the secure connection and reset it: Firefox's Encrypted Client Hello, on by default since Firefox 119, hides that name on sites that support it, but only while DNS over HTTPS is in use (Mozilla). Our guide to networks that block encrypted DNS explains why some networks interfere with it.

Fix 5: Try Troubleshoot Mode and Clear Site Data

• Troubleshoot Mode starts Firefox with add-ons and custom settings disabled: open the menu → Help → Troubleshoot Mode… → Restart. If the site works there, an add-on or setting is to blame.
• Clear the site's data: click the padlock in the address bar → Clear cookies and site data….
• Refresh Firefox as a last resort: open about:support and click Refresh Firefox. It removes add-ons and resets settings but keeps bookmarks, history and saved passwords.

Fix 6: Reset the Network Stack

If every browser on the computer fails, reset its network configuration. On Windows, run these in an administrator Command Prompt, then restart:

netsh winsock reset
netsh int ip reset
netsh winhttp reset proxy
ipconfig /flushdns

On a Mac, remove and re-add the Wi-Fi network and flush the DNS cache.

For Website Owners

If visitors on many networks report PR_CONNECT_RESET_ERROR, something in front of your web server is resetting HTTPS connections. Check whether a firewall, rate limiter or WAF is blocking their IP addresses or countries, whether the server accepts TLS 1.2 and 1.3 handshakes for every hostname it serves, and whether the web server process restarts or crashes. The ERR_CONNECTION_RESET guide covers the server-side checks in detail, and the HTTP Header Checker shows what a successful request returns.

Firefox Error Codes and Their Chrome Equivalents

Full guides: ERR_CONNECTION_CLOSED, ERR_SSL_VERSION_OR_CIPHER_MISMATCH and Your connection is not private for certificate warnings.