Firefox sec_error_expired_certificate after website's SSL is expired

Question

Level 1

13 points

Firefox sec_error_expired_certificate after website's SSL is expired

I'm trying to access one of my website but I'm getting this error on Firefox sec_error_expired_certificate.

Website's certificate expired yesterday 30th March 2019. I've already installed renewed certificate on the server and checked with SSL checker and it all picks up renewed certificate.

On my Mac I keep getting certificate error on all browsers.

The solution mentioned all over the internet says to fix time. My Mac's time is correct as it's already set to "Set date and time automatically".

I've also removed expired old certificate on Keychain Access and imported renewed certificate. Restarted Mac but still having the same issue.

Does anyone know how to fix this annoying issue?

iMac 27", macOS 10.14

Posted on Mar 31, 2019 9:05 AM

Reply

Answer 1

BDAqua

Level 10

250,975 points

Mar 31, 2019 9:12 AM in response to aklion

Maybe a Cache?

To find out if it's system wide or user specific, try this...

Open System Preferences>Users & Groups, unlock the lock, click on the little plus icon, make a new admin account, log out & into the new account.

Does it work in the new account?

Reply

Answer 2

MrHoffman

Level 10

153,501 points

Mar 31, 2019 7:16 PM in response to aklion

You’re going to have to wade into this node.js and socket.io app to figure out how it stores, uses, and caches its certificates.

You can use OpenSSL tool known as s_client to probe the target server and port, and can use that to determine what certificate is being returned.

If you’re off on some random port and particularly a port not under the control of the web server but rather some app, it’ll be probably be the app controlling the certificate, and not the web server.

http://danielnill.com/nodejs-tutorial-with-socketio

Reply

Answer 3

BDAqua

Level 10

250,975 points

Mar 31, 2019 5:52 PM in response to aklion

Open Keychain Assistant, choose Certificate Assistant under the KA menu item. My guess is you have different Certificates.

Reply

Answer 4

BDAqua

Level 10

250,975 points

Mar 31, 2019 3:51 PM in response to aklion

Without the port number it uses port 80, I can only guess without the particulars, but it seems the port you're using is not open on one or both ends.

What do you get trying...

https://www.apple.com:1234

????

Reply

Answer 5

aklion Author

Level 1

13 points

Mar 31, 2019 4:56 PM in response to BDAqua

I'm running socket.io on this port. Port in question is opened and it works, nothing to do with port or server side.

In browser https://example.com shows correct certificate but https://example.com:1234 shows old expired certificate. My question is why this is happening?

Reply