惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

IT之家
IT之家
博客园 - 聂微东
雷峰网
雷峰网
Microsoft Azure Blog
Microsoft Azure Blog
WordPress大学
WordPress大学
Hugging Face - Blog
Hugging Face - Blog
S
SegmentFault 最新的问题
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
Tailwind CSS Blog
博客园 - 三生石上(FineUI控件)
V
Visual Studio Blog
博客园 - 司徒正美
爱范儿
爱范儿
月光博客
月光博客
阮一峰的网络日志
阮一峰的网络日志
博客园_首页
博客园 - 【当耐特】
Jina AI
Jina AI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
酷 壳 – CoolShell
酷 壳 – CoolShell
大猫的无限游戏
大猫的无限游戏
小众软件
小众软件
人人都是产品经理
人人都是产品经理
V
V2EX

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
proxmox CA certificate expired
invalid@exam · 2026-06-17 · via Proxmox Support Forum

term

Well-Known Member

I've been running a cluster for more than 10 years now. Yesterday I added a new node and deleted a old one. The new node's gui does not load because it can't generate certificates, and that is because the proxmox ca certificate has expired. I've tried running pvecm updatecerts -f, and have posted the results from the daily update service below.

The old nodes are still accessible via the web gui and work fine.

What is the proper way to regenerate the CA cert? I believe once that is done, I should be able to go to each node and run pvecm updatecerts -f.

Thanks!

Code:

root@proxmox6:~# pvecm updatecerts -f
(re)generate node files
generate new node certificate
CA expires in less than 2 weeks, unable to generate certificate.

Code:

root@proxmox6:~# systemctl status pve-daily-update.service
● pve-daily-update.service - Daily PVE download activities
     Loaded: loaded (/lib/systemd/system/pve-daily-update.service; static)
     Active: inactive (dead) since Fri 2022-10-28 02:54:37 CDT; 6h ago
TriggeredBy: ● pve-daily-update.timer
    Process: 1526907 ExecStart=/usr/bin/pveupdate (code=exited, status=0/SUCCESS)
   Main PID: 1526907 (code=exited, status=0/SUCCESS)
        CPU: 4.596s

Oct 28 02:54:37 proxmox6 pveupdate[1526907]: <root@pam> end task UPID:proxmox6:00174C97:9CCC761B:635B8AB8:aptupdate::root@pam: OK
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: CN = Proxmox Virtual Environment, OU = 7ab84c1f25372786d53d32760a492a5e, O = PVE Cluster Manager CA
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: error 10 at 1 depth lookup: certificate has expired
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: OU = PVE Cluster Node, O = Proxmox Virtual Environment, CN = proxmox6.telecore.local
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: error 10 at 0 depth lookup: certificate has expired
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: error /etc/pve/nodes/proxmox6/pve-ssl.pem: verification failed
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: Checking/Renewing SSL certificate failed: command '/usr/bin/openssl verify -CAfile /etc/pve/pve-root-ca.pem /etc/pve/nodes/proxmox6/pve-ssl.pem' failed: exit code 2
Oct 28 02:54:37 proxmox6 systemd[1]: pve-daily-update.service: Succeeded.
Oct 28 02:54:37 proxmox6 systemd[1]: Finished Daily PVE download activities.
Oct 28 02:54:37 proxmox6 systemd[1]: pve-daily-update.service: Consumed 4.596s CPU time.

Last edited:

Same problem to me.

Attempt to add node to cluster. All nodes are fully updated to 8.1.4.

Establishing API connection with host '10.193.65.10'
Login succeeded.

check cluster join API version
No cluster network links passed explicitly, fallback to local node IP '10.193.65.35'
Request addition of this node
Join request OK, finishing setup locally
stopping pve-cluster service
backup old database to '/var/lib/pve-cluster/backup/config-1706803133.sql.gz'
waiting for quorum...OK
(re)generate node files
generate new node certificate
TASK ERROR: CA expires in less than 2 weeks, unable to generate certificate.

Altough new node is added to left panel (tree) and is green, but then is WebUI full with "error:0A000086:SSL routines::certificate verify failed (596)" error messages.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This was happen due to CA certificate is too old. It was generated for 10 years and if you have such old cluster, then you have problem.

What helped to me:

On one node - "/etc/pve" is shared filesystem.

cd /root
mkdir oldkeys

mv /etc/pve/pve-root-ca.pem oldkeys
mv /etc/pve/priv/pve-root-ca.key oldkeys
mv /etc/pve/authkey.pub oldkeys
mv /etc/pve/priv/authkey.key oldkeys
mv /etc/pve/priv/authorized_keys oldkeys

And for EACH node in cluster:

mv /etc/pve/nodes/NODENAME/pve-ssl.pem oldkeys
mv /etc/pve/nodes/NODENAME/pve-ssl.key oldkeys

Then run these two commands on EACH node. On first node, because you deleted expired CA, it will create new global CA and also key for local node. Then run them also on all remains nodes. It will find new CA and will generate key for local node only.

pvecm updatecerts -f
systemctl restart pvedaemon pveproxy

I've been running a cluster for more than 10 years now. Yesterday I added a new node and deleted a old one. The new node's gui does not load because it can't generate certificates, and that is because the proxmox ca certificate has expired. I've tried running pvecm updatecerts -f, and have posted the results from the daily update service below.

The old nodes are still accessible via the web gui and work fine.

What is the proper way to regenerate the CA cert? I believe once that is done, I should be able to go to each node and run pvecm updatecerts -f.

Thanks!

Code:

root@proxmox6:~# pvecm updatecerts -f
(re)generate node files
generate new node certificate
CA expires in less than 2 weeks, unable to generate certificate.

Code:

root@proxmox6:~# systemctl status pve-daily-update.service
● pve-daily-update.service - Daily PVE download activities
     Loaded: loaded (/lib/systemd/system/pve-daily-update.service; static)
     Active: inactive (dead) since Fri 2022-10-28 02:54:37 CDT; 6h ago
TriggeredBy: ● pve-daily-update.timer
    Process: 1526907 ExecStart=/usr/bin/pveupdate (code=exited, status=0/SUCCESS)
   Main PID: 1526907 (code=exited, status=0/SUCCESS)
        CPU: 4.596s

Oct 28 02:54:37 proxmox6 pveupdate[1526907]: <root@pam> end task UPID:proxmox6:00174C97:9CCC761B:635B8AB8:aptupdate::root@pam: OK
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: CN = Proxmox Virtual Environment, OU = 7ab84c1f25372786d53d32760a492a5e, O = PVE Cluster Manager CA
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: error 10 at 1 depth lookup: certificate has expired
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: OU = PVE Cluster Node, O = Proxmox Virtual Environment, CN = proxmox6.telecore.local
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: error 10 at 0 depth lookup: certificate has expired
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: error /etc/pve/nodes/proxmox6/pve-ssl.pem: verification failed
Oct 28 02:54:37 proxmox6 pveupdate[1526907]: Checking/Renewing SSL certificate failed: command '/usr/bin/openssl verify -CAfile /etc/pve/pve-root-ca.pem /etc/pve/nodes/proxmox6/pve-ssl.pem' failed: exit code 2
Oct 28 02:54:37 proxmox6 systemd[1]: pve-daily-update.service: Succeeded.
Oct 28 02:54:37 proxmox6 systemd[1]: Finished Daily PVE download activities.
Oct 28 02:54:37 proxmox6 systemd[1]: pve-daily-update.service: Consumed 4.596s CPU time.

Hello, I am here to get some help, i am new to proxmox and i want to know if the SSL Certificate of a node gets expire, what problems we may face ? Web GUI failure ? I did expire the certificate and then tried to load the node in browser, but its working fine.
Can you please tell me about this ?