HELP!!! I messed up my host and now the GUI will not load...

T

TTJames76

New Member
Jul 8, 2025
4
0
1
I was working with ACME trying to generate some new test certificates in the Let's Encrypt Staging Environment and had new certificates generated and loaded. After the GUI reloaded and not it won't load any of my configuration. I knew it had to be something with the new certificates I generated as it was working fine before. I did a bit of hurried research on how to recover and tried several things, none of which worked. In particular, I tried most of what was offer in this post to no avail:
HTML: 
https://forum.proxmox.com/threads/added-ssl-certs-now-cannot-access-web-gui.126208/
I finally decided to go to my nightly backups and replace the pve-ssl.pem and pveproxy-ssl.pem files from backup. I now have the original files in place and restarted the pveproxy service, but the GUI still will not load. I even tried rebooting the host knowing there were VM's running on it, but that did not help. I am a relative newbie to Linux and uber newbie to Proxmox, so I am trying not to panic but I know this must be something simple but I can not figure it out. Can someone please offer some suggestions as to what I could have done wrong and how I could get it back?
 
Hello,

Did you try to regenerate certificate?
pvenode cert regen --force
systemctl restart pveproxy
 
Try with pvenode acme cert renew.
BTW did you have a chance to check journalctl reagrding any issues?
 
First of all, THANK YOU to everyone for your replies. I did try
Code: 
pvecm updatecerts -f
and it did not seem to work. Still received the strange "half loaded" GUI. I have not tried
Code: 
pvenode acme cert renew
or
Code: 
pvenode cert regen --force
yet, but will shortly. I did review journalctl and everything looks good. Nothing out of the ordinary. I must note that I was panicking a bit when this initially occurred and have had time to step back and think logically. Something that occurred to me is that I may have been having a wonky browser caching issue seeing as the suggestions of reissuing the self-signed certs should have worked in my mind. I had a coworker second the caching issue idea, so I am going to try that when I am able to get back to this. Will keep everyone updated. Thanks again for the ideas.
 
UPDATE : This has been resolved. Apparently regenerating the certificates did work, but caused my browser to freak out. I simply opened a fresh incognito browser window today while taking a fresh second look at this and all is loading as expected. Thanks again for everyone's ideas.
 
You must log in or register to reply here.
Top Bottom