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

In FireFox 9, loading secure web pages running on non-standard ports works just fine. In FireFox 10, those same pages do not load and a "The connection was reset" message is displayed.

more options

How can this be fixed so functionality returns as per FF9 and below?

This occurs on any secured website running on a non-standard port, with FF10.

All Replies (4)

more options

Perform the suggestions mentioned in the following articles:

Check and tell if its working.

May not be related to your problem but some of your Firefox Plugins are out-dated

  • Update All your Firefox Plugins ->
  • When Downloading Plugins Update setup files, Remove Checkmark from Downloading other Optional Softwares with your Plugins (e.g. Toolbars, McAfee, Google Chrome, etc.)
more options

< X-Post from >

I don't think this is restricted to Firefox. I've noted this behaviour with IE9, Firefox 10.0.2, Opera Mobile (on my phone) and Chrome(latest version) with my Linksys E3000 router (I access it from https://<IP>) and my 3ware RAID card management suite, 3DM2 (I access it from https://localhost:888 ).

Notably, the only thing amiss that I've been able to see in the certificates (I'm no expert) is that the one from Linksys has issue and expiry dates in 1969 and 1970 respectively. However, I don't think this is the cause since 3DM2 has proper looking issue dates and has the identical problem.

Coincidentally, I noticed this happening after a fresh reinstall of Windows 7 x64 with virtually nothing installed on it (FF, Office 2007), so I don't think it's something wrong with the other software on the machine.

more options

The "The connection was reset" error message can be caused by a bug fix for the BEAST (Browser Exploit Against SSL/TLS) attack that the server doesn't handle.

more options

To solve the problem you should read BUG 702111 ( It's very large and quite technical. In my case the problem was solved adding an environment variable to disable the splitting feature, the one that produces this behavior in FireFox10. NSS_SSL_CBC_RANDOM_IV=0