ProxMox

Edit pageLast modified: 22 December 2024

The ProxMox module implements the Machine, Storage, Network, Config, and Virtualized extensions.

With ProxMox, virtual machines or containers can be created and managed.

Setup

  1. Create new Machine.

    Create Machine

  2. Select ProxMox as Provider

    Select Provider

  3. Prepare Provider Configuration

    • Node → Name of the Node Server of your ProxMox Cluster.

    • Realm → PVE or PAM Authentication.

    • URL → URL to your ProxMox Webinterface Login.

    Note Demo

  4. Save Machine to create a new Instance.

Example configuration

Example configuration

warning

In Production, please don't use the root user, the root login should be disabled for remote login on your hypervisor.

VNC Console

Hostinger uses an internal VNC proxy, which converts the raw VNC TCP stream into a WebSocket stream so that the NoVNC library can process it.

note

If the VNC console is integrated externally via the API, it should be ensured that the route /novnc/** is accessible from the outside.

Limitations

We have decided to use ProxMox's native API and refrain from any tinkering via SSH.

Unfortunately, ProxMox's API is relatively limited when it comes to statistics or consoles.

Additionally, it is not possible to establish a VNC console connection to the hypervisor/node because ProxMox requires an encrypted connection for remote access.

However, this is currently not implemented in the NoVNC library.

ProxMox itself, as of now, establishes this VNC connection for its web interface unencrypted, but this would again require an SSH command, as only encrypted sessions are possible via the API.

note

Qemu Agent calculates the current Disk usage for VMs, you have to enable it, otherwise for the specific VM no Disk Usage is displayed.