Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Firefox 33 cannot open https://mfacilities.betavine.net (sec_error_bad_signature)

  • 1 reply
  • 1 has this problem
  • 5 views
  • Last reply by philipp

robin.summerhill
robin.summerhill
more options

I get a sec_error_bad_signature when trying to open the following URL: https://mfacilities.betavine.net

Using an SSL validation tool the certificate chain seems OK: http://www.networking4all.com/en/support/tools/site+check/report/?fqdn=mfacilities.betavine.net&protocol=https

I understand that the Certificate Verification procedure used by Firefox changed in version 31 (see https://wiki.mozilla.org/SecurityEngineering/Certificate_Verification). A workaround was possible to revert to the old procedure but that has now been removed in version 33.

Any advice on how to diagnose the problem or work around it? The site loads OK with Safari, Chrome and IE.

Robin Summerhill Vodafone UK

I get a sec_error_bad_signature when trying to open the following URL: https://mfacilities.betavine.net Using an SSL validation tool the certificate chain seems OK: http://www.networking4all.com/en/support/tools/site+check/report/?fqdn=mfacilities.betavine.net&protocol=https I understand that the Certificate Verification procedure used by Firefox changed in version 31 (see https://wiki.mozilla.org/SecurityEngineering/Certificate_Verification). A workaround was possible to revert to the old procedure but that has now been removed in version 33. Any advice on how to diagnose the problem or work around it? The site loads OK with Safari, Chrome and IE. Robin Summerhill Vodafone UK

All Replies (1)

philipp
philipp
  • Moderator
more options

hello robin, this site should give you better and more detailed results in order to find out what's wrong with the certificate: https://www.ssllabs.com/ssltest/analyze.html?d=mfacilities.betavine.net&hideResults=on