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.

Error code sec error expired certificate

  • 2 replies
  • 1 has this problem
  • 2 views
  • Last reply by cor-el

madmaxxc
madmaxxc
more options

I am trying to go to this Facebook game site and i get this,,,,, My computers date and time is correct so that can't be the problem, i also took a SS There is no button to click on to bypass this error,,, >>>(i know what i am doing to bypass the error) So how do i get pass this?

[slotmachines.rubyseven.com uses an invalid security certificate.

The certificate expired on 7/6/2015 6:59 PM. The current time is 7/6/2015 7:26 PM.

(Error code: sec_error_expired_certificate)]

thank you

I am trying to go to this Facebook game site and i get this,,,,, My computers date and time is correct so that can't be the problem, i also took a SS There is no button to click on to bypass this error,,, >>>(i know what i am doing to bypass the error) So how do i get pass this? [slotmachines.rubyseven.com uses an invalid security certificate. The certificate expired on 7/6/2015 6:59 PM. The current time is 7/6/2015 7:26 PM. (Error code: sec_error_expired_certificate)] thank you
Attached screenshots

All Replies (2)

guigs
guigs
more options

Hi (Error code: sec_error_expired_certificate)] Go to your stored certs and remove the cert for this site to request a new one. about:preferences#advanced > Certificates > View Certificates

I hope this helps.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

The certificate got updated on July 7th, so you shouldn't be seeing this error. 

Validity: from 07/07/2015 00:00:00 UTC to 07/06/2016 23:59:59 UTC

Modified by cor-el