Proxmox WireGuard VPN in one click

NexoVirt sets up a WireGuard VPN on each Proxmox node with one click and gives every admin named configs that reach the nodes and their private networks. Configs can also be limited to one node or to selected SDN projects, and on Enterprise customers add their own devices that reach only their own servers.

WireGuard VPN in the NexoVirt panel

What it does

A WireGuard VPN per node, named admin configs, project and customer configs.

  • One switch per node

    Turn the VPN on from the node page (Network, WireGuard VPN). The agent installs WireGuard and creates the node key on the node; the private key never leaves it.

  • Subnets that never collide

    Each node gets the next free /24 in 10.88.0.0/16, or a private range you choose. Overlaps with existing networks, IP zones, SDN or NAT are refused with a clear message.

  • Named configs

    Create as many configs as you need: a master config for every node, a config for one node, or one that reaches only selected SDN project networks. Download it or scan the QR code.

  • Readiness checklist

    Each node shows whether the agent, WireGuard, the interface, IP forwarding, the firewall and the public endpoint are ready, and the last handshake.

  • Customer devices

    On Enterprise, customers add their own devices in the portal (5 each by default). A device reaches only the customer's own servers and follows ownership changes automatically.

  • Keys shown once

    The panel keeps public keys only, plus an encrypted preshared key per device. A config is shown once; downloading it again creates new keys and revokes the old ones.

Why not just use the Proxmox web UI?

Proxmox VE runs the virtualization. NexoVirt adds the layer around it. WireGuard VPN, task by task:

TaskProxmox web UINexoVirt
Set up WireGuardInstall packages and write configs on each node by handOne switch per node
Pick a VPN subnetCheck every network yourselfNext free /24, overlaps refused
Let a customer reach only their VMsFirewall rules per customer by handRules generated from guest ownership
Node with a changing IPRun your own DynDNSThe free nxvdns.link name is the endpoint

How to use it

Up and running in 4 steps, all in the panel.

  1. On a node page, open Network and switch on WireGuard VPN.

  2. Open VPN in the sidebar, create a config and download it or scan its QR code with the WireGuard app.

  3. Check the readiness list on the node; behind NAT, forward the UDP port it shows.

  4. On Enterprise, customers add their own devices in the portal.

WireGuard VPN: step-by-step guide in the docs

See it in the panel

Real screenshots from NexoVirt, with demo data.

WireGuard VPN FAQ

What if my Proxmox node is behind NAT?

Forward the WireGuard UDP port (51820 by default) to the node. The readiness checklist shows the exact rule to add on your router.

Can customers reach the Proxmox node through the VPN?

No. Customer devices reach only the servers they own. The node and the panel stay out of reach.

What do clients connect to?

The node's free DynDNS name when DynDNS is on, otherwise an endpoint you set or the node's address.

Start running NexoVirt today

Free for homelabs with unlimited VMs on up to 2 nodes. Running a hosting business? Upgrade in place when you grow, no migration.