大网数据广告活动
服务器运维问答

SSL certificate still appears as expired

· 52CE 我爱测

My ssl certificate has expired and I generated a new one with the same private key. After I uploaded my new certificate on the server, chrome and other browsers still view the old one. Deleted cache and everything, tried in an in…

问题原文

原帖链接 · Claudiu Creanga · CC BY-SA 4.0

My ssl certificate has expired and I generated a new one with the same private key. After I uploaded my new certificate on the server, chrome and other browsers still view the old one. Deleted cache and everything, tried in an incognito window, restarted the express js server. Could it be because I used the same private key?

已采纳解答

原帖链接 · Steffen Ullrich · CC BY-SA 4.0

Deleted cache and everything, tried in an incognito window, restarted the express js server.

Browsers don't cache the server certificate. They might reuse an existing TLS session and not get the new certificate though. But this is only done if the handshake for this connection succeeded, i.e. certificate was valid or the invalid certificate was explicitly accepted. If the browser still complains about the certificate as expired after reloading the page, then the server is still providing the old expired certificate.

Could it be because I used the same private key?

No, it does not matter that the same private key is used.

Make sure that you a) really replaced the old certificate with the new one and b) replaced it on the correct server, i.e. the one which is actually terminating the TLS connection from the client. Depending on your configuration this might be the express js server itself or some reverse proxy or WAF in front of it.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2022-05-27)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。