Søg i 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

more a bug report than a question firefox 10 nolonger mangages https with linksys routers

  • 12 svar
  • 13 har dette problem
  • 9 visninger
  • Seneste svar af Lichsmash

more options

linksys nolonger can mange to conect via https to a home router ie athentacates fine firefox worked with version 9

linksys nolonger can mange to conect via https to a home router ie athentacates fine firefox worked with version 9

Valgt løsning

I followed the instructions in SafeBrowser's link pertaining to the support bulletin from MS ( http://support.microsoft.com/kb/2643584 ) and applied FixIt 50824.

IE9 now works properly. Firefox and Chrome do not.

Læs dette svar i sammenhæng 👍 0

Alle svar (12)

more options

Have you tried it with HTTP Everywhere disabled?

more options

just tested that still fails im hoping someone has simillar if not the same gear and can reproduce this

more options

Do you get any error messages?

Which SSL protocol and encryption cipher is used for that connection?

more options

this router uses a self issued cert for SSL i have no idea on the protocol or cipher

typing in the address as https://home.router.ip.address and hiting go takes me to a security exception page on fire fox due to the self signing after cilcking the confirm exemption that's when it breaks Firefox 9 and lower would display a user name and password entry popup window where as Firefox 10 displays the conection was reset error

more options

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

I've since lost the computer that originally produced this error do to a rare check disk that corrupted my OS partition table it may be that its not just limited to fire fox since i don't run chrome and only use ie to work around this but it may have been the canary in the coal mine as far as this issue

post reinstall i continue to get a "the connection was reset page" id try and sniff the handshake with wireshark but with me barely out of it school i wont know what to look for

more options

Read this thread in the Linksys forum; 5th post from top by Jeffroanderson may be the answer:


If this reply solves your problem, please click "Solved It" next to this reply when signed-in to the forum.

more options

that's interesting to suggest it could be a windows only problem its enough that im dusting of my ubuntu vert. to test the issue

more options

I must correct myself. I was NOT able to replicate this problem on Opera Mobile on my Android phone. I thought I was, but I think the 3DM2 server is set up to only accept local clients. I am able to access my Linksys router fine from Opera Mobile on Android.

more options

Lichsmash said: "that's interesting to suggest it could be a windows only problem..."

It is not a Windows only problem; the article below starts with


If this reply solves your problem, please click "Solved It" next to this reply when signed-in to the forum.

more options

Valgt løsning

I followed the instructions in SafeBrowser's link pertaining to the support bulletin from MS ( http://support.microsoft.com/kb/2643584 ) and applied FixIt 50824.

IE9 now works properly. Firefox and Chrome do not.

more options

if this is a result of mozilla including rfc 6176 in ff10 as i think it is then we can mark this working as intended on this end