Does Proxmox as Single Node on Hetzner make sense?

Yes - for many SMB setups, a properly operated single node is absolutely sensible. What matters is backup concept, restore tests, monitoring, and an update process (instead of "HA at all costs").

What's the key difference between Single Node and HA Cluster?

Single node resolves failures via backup/restore (disaster recovery). An HA cluster restarts HA-managed guests on a remaining node after a node failure. Guests are moved before maintenance; networking, storage and spare capacity must support this.

Do I absolutely need 3 nodes for HA?

For true quorum-based HA, a 3-node design is standard. 2-node setups are possible but need an additional quorum component/design decision (otherwise split-brain risk).

Can I run Proxmox in Hetzner Cloud?

For dev/test and smaller setups, it can work. For stable performance, local NVMe and predictable latencies, Dedicated is often the better foundation.

Which Proxmox version should I use on Hetzner?

Use a stable Proxmox release that matches the Debian base; the Proxmox ISO includes a complete Debian system with Proxmox packages.

How do I install Proxmox VE on a Hetzner Dedicated Server?

Install Debian through the rescue system and add Proxmox, or boot the Proxmox ISO from rescue using QEMU/VNC. Both paths are covered in the Hetzner guide (as of October 2026).

Can I install Proxmox on Hetzner without a KVM console?

Yes. The Hetzner guide covers rescue with QEMU/VNC; the MIT-licensed third-party project ariadata/proxmox-hetzner automates installation. Review the script before running it as root (as of October 2026).

How does Proxmox on Hetzner work with only one public IP?

Guests can use a private bridge network with NAT through the public host IP. Publicly routed guest addresses require additional IPs or subnets; routing does not turn one public IP into several addresses. The Hetzner guide covers masquerading and routed setups (as of October 2026).

What do I need to consider for hostname/FQDN?

Hostname and IP should be final before cluster creation; later changes in cluster context are very unpleasant or not supported.

How do I configure networking on Proxmox - GUI or file?

Proxmox uses the Linux network stack; configuration is possible via GUI or via /etc/network/interfaces. For guests, you typically need Linux bridges (vmbrX).

Which ports do I need to plan for Proxmox Web GUI?

The web GUI is accessible by default via https:// :8006. For remote admin, also plan SSH (22) and control access ideally via allowlist/VPN.

How do I secure the Proxmox Web GUI right after installation?

Don't just expose it to the internet: IP allowlist, VPN/jump host, Proxmox firewall or upstream firewall. Proxmox notes that for remote admin you need rules for GUI (8006) and often SSH (22).

Enterprise Repo vs No-Subscription Repo - which is right?

With subscription, the Enterprise Repository is the recommended, stable path. Without subscription, you use public repos; important is that repos are set correctly so updates work.

Is there a quick standard installation you recommend?

Yes: A single node on Dedicated (NVMe), clean network basics, immediate PBS/backup target, monitoring + documented update process. That gives you a "minimum viable setup" that can grow to a cluster later.

What are Hetzner Cloud Networks / Private Networks?

Private Networks are Layer-3 private links between cloud servers via separate interfaces - ideal for internal traffic like cluster communication or private services.

Does traffic in Hetzner Private Network cost extra?

Cloud Networks and internal traffic are free (Hetzner Networks, as of October 2026).

Is traffic in Hetzner Private Networks automatically encrypted?

No. The private network is isolated but not automatically encrypted. Use TLS or a VPN for sensitive data (Hetzner FAQ, as of October 2026).

Do Hetzner Cloud Networks support IPv6?

Cloud Networks use private IPv4 addresses; plan public IPv6 connectivity separately (Hetzner FAQ, as of October 2026).

How are Private Network interfaces configured on Cloud Servers?

With standard images, the private network interface is automatically configured via DHCP (hc-utils).

Can I integrate Dedicated Servers into Hetzner Cloud Networks?

Yes - Hetzner describes coupling a Robot vSwitch with a Cloud Network (subnet with "vSwitch connection").

What is a vSwitch at Hetzner - and why is it important for Proxmox?

A vSwitch is (depending on use) the foundation for private L2 connectivity and/or coupling between Dedicated and Cloud Networks. For Proxmox, this is relevant for keeping cluster/storage traffic private and controlled.

Why should Corosync have its own network?

Corosync is latency-sensitive; other traffic can cause jitter and affect cluster stability. Best practice is a separate Corosync network; storage traffic should not run on the same network.

Routed vs Bridged: what's "normal" on Hetzner?

On Hetzner, you must take IP/MAC binding seriously; in some scenarios only routed works cleanly. For bridged setups, you may need virtual MACs - otherwise problems up to abuse/block can occur.

How do I test if Corosync is running on the right interface?

We check cluster status, Corosync bindings, and whether traffic really goes through the planned private network (not via public IP). We also validate failover/quorum under load.

What are typical network errors that break HA?

Corosync on an overloaded network (storage/backup/migration), MTU mismatch, "accidentally" public traffic for cluster, or Hetzner-specific MAC/IP misconfiguration.

ZFS or Ceph - which is better for HA?

For single node, ZFS is often the sweet spot: fast, stable, simple. For HA clusters, Ceph is interesting because it provides distributed storage - but requires more planning (network, disks, sizing).

How much storage do I need?

Rule of thumb: plan for 2-3x your current VM data needs plus backup buffer and growth. With Ceph, replication adds up (more raw capacity needed).

Do you offer support/hour packages for Proxmox on Hetzner?

Yes. Proxmox support is billed by effort, and hour packages of 10, 25 or 50 hours are available. For ongoing operations we offer Managed Proxmox.

Install & Run Proxmox on Hetzner

Single node or cluster on suitable dedicated servers, including routing, vSwitch, private networks, storage, backup, and optional managed operations.

Dedicated Server
vSwitch & Private Networks
Single node or cluster

Free Initial Assessment Support & Hour Packages

Reviews

IT Beratung Service Consulting Soforthilfe

Companies worldwide trust WZ-IT

Read client reviews

Proxmox × Hetzner

Why Proxmox on Hetzner?

The combination of Proxmox VE and Hetzner enables an open virtualization architecture. Whether it is more economical than VMware or cloud VMs is assessed from hardware, licensing, migration and operating effort.

Cost
Proxmox VE is open source; commercial subscriptions are optional. Hetzner server prices depend on model and availability and are recalculated for each quote.
EU & GDPR
As of October 2026: dedicated locations in Germany and Finland are selectable. Data flows and subprocessors are reviewed for the specific architecture. Hetzner data centers
Full Control
Root access, custom network configuration, no dependency on cloud provider APIs.
Performance
The server is not shared with other customers: CPU, RAM and disks are dedicated to your Proxmox environment, so there is no noisy-neighbour effect from other customers. Performance depends on hardware, storage and workload.
Typical Use Cases
Private Cloud · Kubernetes Nodes · Legacy VMs · VDI · Dev/Staging/Prod

Architecture

Architecture Options

Which architecture fits your requirements? We help with the decision.

Single Node

Option 1: Single Node Proxmox on Hetzner Dedicated

Simple setup & management
Full dedicated hardware
Predictable monthly costs
Ideal for SMB & dev/test

One dedicated server for smaller workloads or cost focus. Dedicated resources, simple setup, clear responsibility.

Recommended

Option 2: Proxmox Cluster on Hetzner Dedicated (HA)

VM restart after node failure
Live migration without a VM restart
Move guests before maintenance
Coordinate quorum and storage

From three nodes: HA restarts guests after a node failure. Live migration moves running VMs without a restart. Quorum, storage and spare capacity are prerequisites.

Hybrid

Option 3: Hybrid - Cloud + Dedicated

Flexible access
Private networks + vSwitch
Jump server in cloud
Workloads on dedicated

Management/bastion in Hetzner Cloud, workloads on dedicated servers. vSwitch connects both worlds.

Single Node Setup - Best Practice
Single Node vs HA Cluster	Single Node	HA Cluster (3+ Nodes)
When Single Node Makes Sense	Budget focus, simpler management, manageable workloads	Automatic failover
Setup	Simple setup & management	Live migration without a VM restart
Cost and maintenance	Lower costs	Move guests before node maintenance
Failure	Backup/restore as DR strategy	Failover on node failure

≠Single Node ≠ Insecure: Professionally operated with backups, restore tests and monitoring. Upgrade Path to HA: Can be expanded to cluster anytime when requirements grow.
·Proxmox works as single node or as cluster. For many SMB setups, a properly operated single-node system is sufficient - what matters is backups, monitoring and documented updates.

Scope

Network Setup with Private Networks & vSwitch

What we set up on Hetzner: network, cluster and high availability as well as backup, updates and monitoring.

Network Design on Hetzner

As of October 2026: Private Networks use IPv4; internal traffic is free and not automatically encrypted. Hetzner FAQ · Networks

Hetzner Cloud Networks (Private Networks)
Private Networks (Hetzner Cloud): Private IPs, not internet-routed, L3 links. Ideal for cluster communication and management traffic. Private Layer-3 links between cloud servers. Traffic in network is free. Not automatically encrypted → use TLS/VPN. IPv4; IP assignment via Hetzner backend.
vSwitch (Dedicated ↔ Cloud)
Connects dedicated servers with cloud private networks. Layer-2 connection for seamless communication. Virtual Layer-2 network for L2 segments/VLAN flows. Important for keeping cluster/storage traffic private.
Hetzner Special: Routed vs Bridged Setup
Hetzner uses strict IP/MAC binding. Depending on setup, routed setups are required; for bridging you need virtual MACs - otherwise packets may end up as "abuse". For bridged (vmbr0 directly on physical NIC): Set vMACs in Robot Panel, otherwise Hetzner routing discards your frames. For routed: Consider IP forwarding.

Network separation

Management, cluster/Corosync and storage on separate networks for security and performance.

Management
Web GUI, SSH, API access. Web GUI/SSH (strictly limited, ideally via VPN/jump host)
Cluster/Corosync
Heartbeat, quorum, cluster sync. Exclusive, quiet link (Private Network / vSwitch / dedicated NIC)
Storage (optional)
Ceph, NFS, iSCSI traffic. Separated (Ceph/NFS/iSCSI), not on Corosync link

Cluster & High Availability

The HA manager restarts HA-managed guests on remaining nodes after a node failure. We configure the cluster and HA for you.

Cluster Setup
pvecm, naming concept, network requirements
HA Manager
Automatic restart of VMs and containers after node failure
Quorum & Split-Brain
3-node recommendation, QDevice for 2-node setups
ZFS (Lokal)
Local disks support live migration. HA with ZFS replication can lose changes since the last successful replication (RPO). Shared storage is an alternative. Replication, Live-Migration.
Ceph (Verteilt)
Shared storage, HA-friendly, self-healing. More complex, requires dedicated network. Recommended for HA clusters.

Backup, Updates, Monitoring

Professional operations mean: automation, monitoring, documented processes.

Backup Strategy
Proxmox Backup Server (PBS), defined RPO/RTO, immutable & offsite backups, regular restore tests
Update Management
Rolling updates, documented runbooks, coordinated maintenance windows, rollback plans
Monitoring & Alerting
Host/VM/storage metrics, backup job monitoring, alerting on issues, capacity planning

Install Proxmox on Hetzner: prerequisites and procedure

1. Activate rescue: Choose single node or HA; verify access and backups, activate rescue in Robot.
2. Choose installation path: Set hostname; assess Debian plus Proxmox or ISO/script, size storage. Commands in the guide.
3. Configure networking: Check IP plan, routing/NAT and MAC binding; account for private networks and cloud DHCP.
4. Harden access: Protect GUI/SSH with VPN or allowlist; configure backup and monitoring.
5. Optionally build a cluster: For HA (pvecm create, pvecm add): separate Corosync from storage, test quorum and failover; agree migration and operations.

Hetzner specifics

Common Installation Errors & Troubleshooting

Hetzner-specific problems and their solutions. The cleaner your prechecks, the fewer mysterious cluster problems later - especially with Corosync and storage.

Dedicated vs Cloud - What's Different?

Hetzner Dedicated

Full hardware control, local NVMe
Rescue system for installation
vSwitch for L2 connectivity

Dedicated vs Cloud - What's Different?

Hetzner Cloud

Fast provisioning, API-driven
Private Networks (L3) automatic via DHCP
Ideal for dev/test, jump servers

Problem	Cause	Solution
Proxmox installed but no network after reboot	Wrong interface name/config after ISO install via rescue/QEMU	Set interface names correctly before reboot (follow Hetzner documentation)
VMs have network, then suddenly gone / abuse warning	Bridged setup without proper (virtual) MAC binding	Set vMACs in Robot Panel or switch to routed setup
Cluster misbehaves / nodes flapping	Corosync running on overloaded network (storage/backup/migration)	Set up separate Corosync network (Private Network/vSwitch)
Private network feels secure but data unencrypted	Hetzner Cloud Networks are private but not automatically encrypted	Use application TLS or VPN/WireGuard

Operating models

Support & Operating Models

Setup with handover, shared operations or fully managed: you decide what stays with your team.

Managed Proxmoxfrom €179.90 excl. VAT / node and monthWe handle complete operations: monitoring, updates, backups, support - you focus on your business.

Fully Managed

Monitoring
Updates
Backups
Support

Free Initial Assessment Proxmox maintenance and operations Configure a non-binding request

Payment

Bank transfer

Other routes

One-time Setup

We set up your Proxmox cluster, document everything and hand over to your team.

View Proxmox setup →Billed by time

Co-Managed

Your team handles daily operations, we support with updates, troubleshooting and expansions.

€120 excl. VAT / hour · Hour packages from €1,200 excl. VATDescribe the task →For professional secrecy holders

Operate Proxmox in the Section 203 Managed Cloud

If Proxmox processes client, patient or other professional secrets, WZ-IT plans the application, infrastructure, access, backups and ongoing operations within a purpose-built operating model.

View the Section 203 Managed Cloud →

Frequently Asked Questions

Proxmox on Hetzner - Answers to Your Questions

TopicsBasics & Selection Installation & Setup Hetzner Network & vSwitch Cluster & HA Operations Support & Operations

Basics & Selection

Installation & Setup

Hetzner Network & vSwitch

Cluster & HA Operations

Support & Operations

Knowledge

Proxmox proof from real projects

Customer feedback on virtualization, backup, VPN, security and ongoing cluster operations.

Networking & Provisioning

WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.

Steve KirchnerManaging Director, nextGYM GmbH

View project

International

Built in Germany's Ruhr Valley. Running worldwide.

WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.