You open a page in Firefox and get PR_END_OF_FILE_ERROR instead. That code means the encrypted connection broke before Firefox could verify what came back, so there's no button to click through.
Start with the outside-in tests: a private window, a second browser, another site. Then work through proxy settings, DNS over HTTPS, extensions, and antivirus HTTPS scanning until the page loads again.
In this guide, I have covered:
Contents
What PR_END_OF_FILE_ERROR means when Firefox can’t open a site
You typed an address, or clicked a link, and Firefox answered with an error code instead of the page. PR_END_OF_FILE_ERROR appears when a secure connection ends in the middle of the handshake and Firefox can’t verify what came back from the site.
That is not the same as a plain “site cannot be reached” message. The failure happens inside the encrypted part of the connection, after Firefox has already reached the server.
Mozilla lists the usual causes: a proxy, DNS over HTTPS, a VPN, antivirus or firewall software that inspects encrypted traffic, and security appliances on your network. The error can also hit a single site, so test Firefox and a second browser before you change anything.
There is no safe “bypass this warning” option for this code. If the checks below don’t clear it, the site owner or your network administrator has to look at the certificate and HTTPS configuration on their end.
Quickly identify where the failure starts
Before you touch a setting, work out which part of the chain is broken: Firefox, your network, or one website.
- Open a new private window in Firefox and try loading the affected address.
- Try the same address in a different browser on the same computer.
- Try another website in Firefox, such as a site you normally visit without trouble.
A second browser failing too points at the network, a proxy, or security software, not at Firefox. Failing on one site in every browser is the site owner’s problem to fix. Failing in Firefox alone? Keep going with the settings checks below.
Check Firefox proxy and connection settings
Your proxy settings are worth checking first, because Firefox keeps its own copy of them. One stale address there is enough to break every secure connection you open.
- Open the Firefox
menu and select Settings. - Scroll to the General section and find Network Settings.
- Select the Connection Settings button.
- Choose No Proxy unless you know this network requires a specific proxy.
- Select , restart Firefox, and load the affected website again.
You’ll know it worked when the page loads with No Proxy selected.
If your organization runs a proxy, don’t remove it. Confirm the server and port with your network administrator, then retest with the corrected values.
Test DNS over HTTPS
DNS is one of the few parts of the connection Firefox handles itself. Encrypting those lookups can clash with a network or a security appliance that wants to see them.
- Open the Firefox
menu and select Settings. - Open Privacy & Security.
- Scroll to Connection and software security, then select Advanced settings.
- Find DNS over HTTPS and select Advanced settings.
- Select Off temporarily, restart Firefox, and test the site.
- If the site loads, leave the setting off or ask your network administrator whether DNS over HTTPS is supported.
The page loading with the setting off tells you DNS over HTTPS was involved. Don’t swap DNS providers while you test. One temporary change settles the question.
Use Troubleshoot Mode to rule out extensions
An extension can rewrite requests or intercept connections even when every Firefox setting looks correct. Troubleshoot Mode starts Firefox without most extensions and custom themes, which makes it a clean test.
- Open the Firefox
menu. - Select Help.
- Select More Troubleshooting Information.
- Select Run Troubleshoot Mode.
- Select and let Firefox restart.
- Load the affected website in Troubleshoot Mode.
A page that loads in Troubleshoot Mode points straight at an extension. Re-enable them one at a time, test after each, and you’ll land on the one causing it. For a fuller walkthrough, see how to disable extensions in Firefox on your computer.
Troubleshoot Mode is temporary. Your extensions and themes return the next time you start Firefox normally.
Check antivirus and firewall HTTPS inspection
Antivirus and firewall suites scan encrypted traffic by installing their own certificate and standing in the middle of the connection. When that feature misfires, it can end the connection before Firefox ever verifies the site.
- Open your antivirus or firewall’s security settings.
- Look for options labeled HTTPS scanning, SSL inspection, encrypted traffic scanning, or web filtering.
- Disable that inspection temporarily, or add the affected site to the software’s exclusion list following its documentation.
- Close and reopen Firefox, then test the site.
- Re-enable the feature after the test unless your security administrator confirms it can stay off.
On a work or school computer, ask the administrator to check VPN clients, network security appliances, and HTTPS inspection policies. Don’t bypass an organization-managed control without approval.
If the failing page is your bank’s, Firefox not loading online banking sites on PC covers the PC-side fixes for that case.
Reset Firefox’s network-related profile state
A refresh makes sense when the error appeared right after a profile change, an update, or a run of extension installs. Try it only after the proxy, DNS over HTTPS, and extension checks above.
- Open the Firefox
menu. - Select Help.
- Select More Troubleshooting Information.
- Select Refresh Firefox.
- Confirm the refresh and wait for Firefox to restart.
- Test the affected website after the restart.
A refresh resets Firefox settings and turns extensions off, but it keeps your saved passwords, bookmarks, and history. If the error comes back the moment you retest, the cause sits outside the Firefox profile.
Verify the network and restart the computer
A VPN client, a stale network adapter, or a router rule can cut encrypted connections without a single change inside Firefox.
- Disconnect and reconnect your network connection.
- Disconnect any VPN client temporarily and test the site again.
- Restart the computer and test the site once it boots.
- Load the same site from another device on the same network, if you have one.
Working on another device but not on this computer narrows it to this machine’s security software and network configuration. Failing on several devices points at the site’s server or the network’s HTTPS filtering.
When to contact the website or network administrator
Some failures aren’t yours to fix. Firefox can’t repair a server certificate or a network policy that rejects encrypted traffic.
Contact the site owner when every browser reports a certificate or secure-connection error for one address. Contact your network administrator when the error shows up on multiple sites, on a work-managed device, or only on the office network.
Include the exact error code, the address that failed, and the time you tried. That saves a round of guessing between HTTPS interception, DNS, proxy, and an expired server certificate.
Frequently Asked Questions
Does PR_END_OF_FILE_ERROR mean the website is permanently down?
No. It usually means the secure connection was interrupted or altered before Firefox could verify the response. A site outage, DNS issue, proxy, or HTTPS inspection feature can all produce similar symptoms.
Can I bypass the PR_END_OF_FILE_ERROR warning?
Firefox does not provide a security exception for this error. Fix the network, proxy, DNS, extension, or antivirus interference instead of bypassing the secure-connection warning.
Should I disable HTTPS-Only Mode in Firefox?
Try that only if you have confirmed that the site works over HTTP and the site is one you trust. HTTPS-Only Mode can prevent insecure connections, but changing it is not the normal fix for PR_END_OF_FILE_ERROR.
Why does the error happen only in Firefox?
Firefox may be using a proxy, DNS over HTTPS, or an extension that the other browser does not use. Troubleshoot Mode and a private window are the fastest ways to check for a Firefox-specific cause.
Will clearing Firefox cookies fix this error?
Usually, no. PR_END_OF_FILE_ERROR occurs during the encrypted connection, before the website’s cookies are needed. Focus on proxy settings, DNS over HTTPS, extensions, security software, and the network instead.
