Search results

Rolling back to a much older kernel and then pinning it is NOT a solution. It's a work around. Has the issue been acknowledged by Proxmox? It won't be fixed until a contemporary kernel they ship has been patched with a fix.

Running into this same issue on Dell R530 dual socket Intel-based systems (E5-2620). Happens periodically on a few of my host nodes. May be related to higher network load.

I still haven't found a fix for this and continue to use noVNC. :(

Ok, restored all of the files back to what they were before I tried this fix... and at least I'm back to my previous state of breakage... with the web interface working for all nodes. Back to the drawing board. Ok, restored all of the files back to what they were before I tried this fix... and...

ARGH. Now I can't connect to half of my nodes with the web interface because of cert errors. That's what I dislike, trying to improve something and only making it worse.

Well, I tried that... first on the working node... no change... then on multiple broken nodes... and no change. The working one is still working and the non-working ones are still not working. :(

I found one forum post (https://forum.proxmox.com/threads/lets-encrypt-on-a-multi-node-cluster.65356/) where a user had one working node and all of the others weren't... and Fabian said to run "pvecm updatecerts" on the node that was working. The user didn't actually try that an restored...

MobaXterm is a nice multi-protocol program which includes SSH and bundles an X11 server for Windows. It makes accessing remote graphical X11 applications on Windows easy.

I run the following command on all of my nodes: $ openssl verify -CAfile /etc/pve/pve-root-ca.pem /etc/pve/local/pve-ssl.pem They all return errors except for one node that is "OK". The OK node works. How do I fix the broken ones?

Greetings, I have a cluster with a few nodes. One of the nodes was accessible to the outside world so I decided to give Let's Encrypt a try within the PVE web interface... and successfully got it working with a LE cert my browsers liked. Then when it came time to renew I discovered that the...