[SOLVED] No Gui Error code: SEC_ERROR_UNKNOWN_ISSUER

[slmac]

I have a new node that was set up a few months ago and have had a few Gui problems. Now Gui does not show and I get a Error code: SEC_ERROR_UNKNOWN_ISSUER.

I got this similar problem on another node earlier this year and fixed it but don't remember how.

pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-5-pve)
pve-manager: 8.3.1 (running version: 8.3.1/fb48e850ef9dde27)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-5
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4

systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: active (running) since Thu 2024-12-12 15:55:08 EST; 5min ago
Process: 976 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 984 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 987 (pveproxy)
Tasks: 4 (limit: 76735)
Memory: 195.1M
CPU: 2.250s
CGroup: /system.slice/pveproxy.service
├─987 pveproxy
├─988 "pveproxy worker"
├─989 "pveproxy worker"
└─990 "pveproxy worker"

Dec 12 15:55:07 dieter systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Dec 12 15:55:07 dieter pvecm[977]: got inotify poll request in wrong process - disabling inotify
Dec 12 15:55:08 dieter pveproxy[987]: starting server
Dec 12 15:55:08 dieter pveproxy[987]: starting 3 worker(s)
Dec 12 15:55:08 dieter pveproxy[987]: worker 988 started
Dec 12 15:55:08 dieter pveproxy[987]: worker 989 started
Dec 12 15:55:08 dieter pveproxy[987]: worker 990 started
Dec 12 15:55:08 dieter systemd[1]: Started pveproxy.service - PVE API Proxy Server.

systemctl status pvedaemon
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
Active: active (running) since Thu 2024-12-12 15:55:07 EST; 22min ago
Process: 932 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 971 (pvedaemon)
Tasks: 4 (limit: 76735)
Memory: 165.4M
CPU: 1.102s
CGroup: /system.slice/pvedaemon.service
├─971 pvedaemon
├─972 "pvedaemon worker"
├─973 "pvedaemon worker"
└─974 "pvedaemon worker"

Dec 12 15:55:06 dieter systemd[1]: Starting pvedaemon.service - PVE API Daemon...
Dec 12 15:55:07 dieter pvedaemon[971]: starting server
Dec 12 15:55:07 dieter pvedaemon[971]: starting 3 worker(s)
Dec 12 15:55:07 dieter pvedaemon[971]: worker 972 started
Dec 12 15:55:07 dieter pvedaemon[971]: worker 973 started
Dec 12 15:55:07 dieter pvedaemon[971]: worker 974 started
Dec 12 15:55:07 dieter systemd[1]: Started pvedaemon.service - PVE API Daemon.

 

[fabian]

if you are using the default, self-signed certificate that is normal - your browser won't know the cluster CA, you have to either mark it as trusted or click away the unknown issuer warning..

 

[slmac]

Fabian.... this suddenly started happening on one of Proxmox servers! Can someone else help!

 

[slmac]

Not sure if it is Proxmox. Cleaned MB, Memory and HD. Reinstalled Proxmox, Changed Ethernet cable and port on router and finally it worked.
Today I logged in and got the same error. Is there a way to check the the Ethernet port all the way to the router?

 

[fabian]

I already gave you the answer above - please read it

more information can be found in the docs: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_certificate_management

 

[slmac]

Fabian, Thank You. We can close this post. The issue was a faulty Ethernet cable. It was a pain to find the cause!

 

[UdoB]

We can close this post.

You can do that by yourself: edit the first post and you'll find a drop-down menu left of the title...