If you prefer a dedicated VNC app, for example for its scaling, clipboard or multi-monitor features, Aprox can hand a guest's console to it. On the Mac, Aprox runs a small local bridge and opens your VNC viewer. On Android, Aprox opens your installed VNC app straight to the node and shows the one-time password. The external viewer is part of Aprox Pro and works for virtual machines and containers.

Where to find it

  1. Open Settings (Mac: Aprox › Settings…, ⌘,).
  2. Set Graphical Console to External VNC viewer for virtual machines with a display. To use it for containers and serial-display VMs as well, set Serial Console to External VNC viewer.
  3. Open the guest's console as usual. See Console.

On iPhone and iPad this type is not available: the console shows External viewers require macOS. and the button is disabled. Choose noVNC or Built-in VNC there instead.

Use an external viewer on the Mac

  1. Select the guest, for example plex, and open its console window (⇧⌘K, or Open Console).
  2. The window reads "Open this VM with an external VNC viewer." and explains: "Aprox will start a local bridge to the PVE VNC websocket and ask the system to open the connection."
  3. Click Open in External Viewer. Aprox shows Starting bridge….
  4. When the bridge is up, the window shows Bridge running and the address, for example vnc://127.0.0.1:59012. macOS opens the address in your default VNC viewer, such as Screen Sharing.
  5. Aprox passes Proxmox's one-time ticket as the password, and most viewers use it automatically. If your viewer asks, "Use the ticket from the connection as the password."
  6. When you are done, close the viewer and click Stop Bridge.

Manage running bridges

Every running bridge is also listed in Settings › Active VNC bridges, each with a Stop button. The section is shown only while a bridge runs.

If it fails

Could not start bridge names the reason. Click Try Again. Common causes are a server signed in with an API token instead of a password, or a missing VM.Console privilege.

Use an external viewer on Android

  1. Install a VNC app that handles vnc:// links.
  2. Open the guest's Console tab. It reads Open in an external VNC viewer: "Aprox asks the node for a VNC ticket and hands the connection to whichever viewer you have installed. The viewer must be able to reach the node directly."
  3. Tap Open in viewer.
  4. Aprox shows Use this as the password: … with the one-time ticket, and opens your VNC app with the node's address.
  5. Enter the ticket as the password in your VNC app if it asks.

If no app on the device handles vnc:// links, Aprox says No app on this device handles vnc:// links. If the node refuses, it says The node would not issue a VNC ticket.

Important

On Android the VNC app connects to the node itself, not through Aprox. Your phone or tablet must be able to reach the node's VNC port directly, for example on the same network or over a VPN.

How it works

Mac Android
Connection Through a local bridge in Aprox, from the viewer to 127.0.0.1 and on to Proxmox over the encrypted Proxmox connection Directly from the VNC app to the node
Password The one-time Proxmox ticket, passed in the address The one-time Proxmox ticket, shown by Aprox
Reachability Only Aprox needs to reach the server The VNC app must reach the node

Security

  • Mac: the bridge listens on 127.0.0.1 only, so no other device can connect to it. It accepts exactly one connection and closes when that connection ends.
  • Both: the ticket is issued by Proxmox for this one console session and expires shortly after.

Requirements

  • Aprox Pro.
  • A password login. Proxmox does not accept API tokens for console connections.
  • Typically the VM.Console privilege on the guest.
  • Virtual machines and containers only. Node shells always open in xterm.js inside Aprox ("External VNC is only available for VMs and containers.").