What about the pveproxy service? I forgot about that in my last reply.

Are you using https? https://10.47....:8006?
 
Yes, I am using https.
root@server:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-12-27 19:22:19 CST; 10h ago
Process: 1435 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 1437 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 1439 (pveproxy)
Tasks: 4 (limit: 4915)
Memory: 135.9M
CGroup: /system.slice/pveproxy.service
├─1439 pveproxy
├─1440 pveproxy worker
├─1441 pveproxy worker
└─1442 pveproxy worker

Dec 27 19:22:19 server systemd[1]: Starting PVE API Proxy Server...
Dec 27 19:22:19 server pveproxy[1439]: starting server
Dec 27 19:22:19 server pveproxy[1439]: starting 3 worker(s)
Dec 27 19:22:19 server pveproxy[1439]: worker 1440 started
Dec 27 19:22:19 server pveproxy[1439]: worker 1441 started
Dec 27 19:22:19 server pveproxy[1439]: worker 1442 started
Dec 27 19:22:19 server systemd[1]: Started PVE API Proxy Server.
 
I just refreshed the page and it came up. I had rebooted it a few times, not sure if something just shook loose. Thank you for your help.
 
  • Like
Reactions: aaron
I just refreshed the page and it came up. I had rebooted it a few times, not sure if something just shook loose. Thank you for your help.
Good to hear that it works. Most likely it was some kind of caching that interfered.

I marked the thread as solved. You can do this yourself as well by editing the first post and selecting the prefix in the drop down menu next to the title :)