PVE Tips

xterm.js in place of noVNC

So...

An issue with noVNC...

It kinda sucks for CLI-only VMs. It doesn't allow for copy-pasta.

Solution, configure the VM to use xterm.js instead.

The grub edits in that article don't seem to work properly tho...

Instead:

GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200 earlyprintk=ttyS0,115200 consoleblank=0"
GRUB_TERMINAL="console serial"
GRUB_SERIAL_COMMAND="serial --speed=115200"

(initially from here)

For some reason, Proxmox leaves noVNC as the console in the UI window & it does weird stuff to the console window when you open it. MRIN...

FFS...

To open the console of a VM set up this way, either click the ">_ Console" button or right-click the VM in the left pane & select ">_ Console" from the menu.

Manually installing REAL certs

I keep copies of my certs on a local webserver that acts as a proxy to feed HTTPS connections to various local servers. This makes it fairly trivial to pull certs to various machines that need them.  Also, I'm using wildcard certs, which simplifies life.

Step 1: Log into the servers shell as root. (either through the Web UI or SSH)

Step 2: Follow along with this list of commands (adjusting appropriately...)

• cd /etc/pve/nodes/
• cd NODENAME
• cp pveproxy-ssl.key pveproxy-ssl.key.BAK
• cp pveproxy-ssl.pem pveproxy-ssl.pem.BAK
• scp USER@WEBSERVER:/etc/apache2/certs/fullchain_YOURDOMAIN.TLD.crt pveproxy-ssl.pem
• scp USER@WEBSERVER:/etc/apache2/certs/YOURDOMAIN.TLD.key pveproxy-ssl.key
• systemctl restart pveproxy

Note: "/etc/apache2/certs" must be readable by USER & USER must also have SSH access to WEBSERVER

Step 3: Enjoy browsing to the Web UI of your server without being bitched at by your browser.

This will also work just fine with machine-specific certs.  You'll need to adjust the filenames of your crt & key files.

(these instructions are currently based on a non-clustered server...)

Convert a physical computer to a proxmox VM

From the Proxmox forums