[SOLVED] PVE mach Probleme nach Reboot/Neustart

J

jimmij

New Member
Mar 30, 2020
9
0
1
45
Hallo zusammen,

ich bin komplett neu bei Proxmox und habe mir auf einen Desktop PC einen kleinen Homeserver aufgesetzt.
i3 - 8GB RAM - SSD 250GB - HDD 2TB Speicher
Habe das aktuelle PVE installiert und im Anschluss einen LXC auf dem läuft eine Nextcloud und eine Virtuelle Maschine mit Ubuntu.
Zusätzlich habe ist ein NAS als Backupspeicher (NFS) eingerichtet.

Dies ist alles in den letzten 3-4 Tagen passiert und seitdem lief der Server wunderbar.

Ich musste gestern das NAS kurz herunterfahren und habe dies dann kurz darauf wieder gestartet.
als ich mich dann wieder in das Webinterface des Server eingeloggt habe, wurde das NAS nicht mehr erkannt.
Also habe ich den LXC und die VM runtergefahren und wollte den Server einfach mal neustarten, das erstemal überhaupt.
Seitdem kann ich den LXC und die VM nicht mehr starten.
Der Server scheint hochzufahren, ich kann per SSH auf die Konsole und auch per Webinterface einloggen - siehe Foto

1.jpg

Auch die Festplatten sind erreichbar per SSH.

Die ersten paar Minuten, nach dem Neustart ist bei der Node-home auch noch ein grüner Haken, aber dann kommt dort ebenfalls das graue Fragezeichen.
Es macht irgendwie den Anschein, als wären die Festplatten nicht erreichbar?

Bin um jede Hilfe dankbar, leider habe ich dazu im AdminGuide und im Forum bisher nichts gefunden.
Vielen dank und Grüße
 
Vielen Dank für die schnelle Antworten!
Ich muss dazu sagen, dass ich mich erst vor ein paar Monaten von Windows getrennt habe und mich nach und nach einarbeite, also bitte habt etwas Geduld mit mir :)

daschmidt94 said:
Sieh dir mal die fstab an NFS kann probleme machen
Click to expand...

fstab gibt mir folgendes: - sollte dort nicht die 2TB HDD und auch das NAS gemountet werden?

Code: 
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
UUID=1B64-5C63 /boot/efi vfat defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

hier noch lsblk:

Code: 
NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                            8:0    0 223.6G  0 disk
├─sda1                         8:1    0  1007K  0 part
├─sda2                         8:2    0   512M  0 part /boot/efi
└─sda3                         8:3    0 223.1G  0 part
  ├─pve-swap                 253:0    0     7G  0 lvm  [SWAP]
  ├─pve-root                 253:1    0  55.8G  0 lvm  /
  ├─pve-data_tmeta           253:2    0   1.5G  0 lvm 
  │ └─pve-data-tpool         253:4    0 141.4G  0 lvm 
  │   ├─pve-data             253:5    0 141.4G  0 lvm 
  │   ├─pve-vm--101--disk--0 253:6    0    10G  0 lvm 
  │   └─pve-vm--102--disk--0 253:7    0    20G  0 lvm 
  └─pve-data_tdata           253:3    0 141.4G  0 lvm 
    └─pve-data-tpool         253:4    0 141.4G  0 lvm 
      ├─pve-data             253:5    0 141.4G  0 lvm 
      ├─pve-vm--101--disk--0 253:6    0    10G  0 lvm 
      └─pve-vm--102--disk--0 253:7    0    20G  0 lvm 
sdb                            8:16   0   1.8T  0 disk
├─sdb1                         8:17   0   1.8T  0 part
└─sdb9                         8:25   0     8M  0 part
 
Zum Syslog:

Code: 
Mar 31 10:39:27 home rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="848" x-info="https://www.rsyslog.com"] rs
yslogd was HUPed
Mar 31 10:39:27 home systemd[1]: Started Login Service.
Mar 31 10:39:27 home systemd[1]: logrotate.service: Succeeded.
Mar 31 10:39:27 home systemd[1]: Started Rotate log files.
Mar 31 10:39:27 home rrdcached[979]: rrdcached started.
Mar 31 10:39:27 home systemd[1]: Started LSB: start or stop rrdcached.
Mar 31 10:39:28 home systemd[1]: Starting The Proxmox VE cluster filesystem...
Mar 31 10:39:28 home zed: eid=2 class=config_sync pool_guid=0xEA6D9DBF68B5E2C5 
Mar 31 10:39:28 home systemd[1]: Started LXC Container Initialization and Autoboot Code.
Mar 31 10:39:28 home zed: eid=3 class=pool_import pool_guid=0xEA6D9DBF68B5E2C5 
Mar 31 10:39:28 home postfix/postfix-script[1159]: warning: symlink leaves directory: /etc/postfix/./makedefs.out
Mar 31 10:39:28 home postfix/postfix-script[1209]: starting the Postfix mail system
Mar 31 10:39:28 home postfix/master[1213]: daemon started -- version 3.4.8, configuration /etc/postfix
Mar 31 10:39:28 home systemd[1]: Started Postfix Mail Transport Agent (instance -).
Mar 31 10:39:28 home systemd[1]: Starting Postfix Mail Transport Agent...
Mar 31 10:39:28 home systemd[1]: Started Postfix Mail Transport Agent.
Mar 31 10:39:28 home systemd[1]: apt-daily.service: Succeeded.
Mar 31 10:39:28 home systemd[1]: Started Daily apt download activities.
Mar 31 10:39:28 home systemd[1]: Starting Daily apt upgrade and clean activities...
Mar 31 10:39:28 home zed: eid=4 class=history_event pool_guid=0xEA6D9DBF68B5E2C5 
Mar 31 10:39:28 home zed: eid=5 class=config_sync pool_guid=0xEA6D9DBF68B5E2C5 
Mar 31 10:39:28 home systemd[1]: apt-daily-upgrade.service: Succeeded.
Mar 31 10:39:28 home systemd[1]: Started Daily apt upgrade and clean activities.
Mar 31 10:39:28 home iscsid: iSCSI daemon with pid=964 started!
Mar 31 10:39:29 home systemd[1]: Started The Proxmox VE cluster filesystem.
Mar 31 10:39:29 home systemd[1]: Starting Daily PVE download activities...
Mar 31 10:39:29 home systemd[1]: Starting PVE Status Daemon...
Mar 31 10:39:29 home systemd[1]: Started Regular background program processing daemon.
Mar 31 10:39:29 home systemd[1]: Starting Proxmox VE firewall...
Mar 31 10:39:29 home systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Mar 31 10:39:29 home systemd[1]: Starting PVE API Daemon...
Mar 31 10:39:29 home cron[1291]: (CRON) INFO (pidfile fd = 3)
Mar 31 10:39:29 home cron[1291]: (CRON) INFO (Running @reboot jobs)
Mar 31 10:39:30 home pve-firewall[1297]: starting server
Mar 31 10:39:30 home systemd[1]: Started Proxmox VE firewall.
Mar 31 10:39:30 home pvestatd[1299]: starting server
Mar 31 10:39:30 home systemd[1]: Started PVE Status Daemon.
Mar 31 10:39:30 home pvedaemon[1322]: starting server
Mar 31 10:39:30 home pvedaemon[1322]: starting 3 worker(s)
Mar 31 10:39:30 home pvedaemon[1322]: worker 1323 started
Mar 31 10:39:30 home pvedaemon[1322]: worker 1324 started
Mar 31 10:39:30 home pvedaemon[1322]: worker 1325 started
Mar 31 10:39:30 home systemd[1]: Started PVE API Daemon.
Mar 31 10:39:30 home systemd[1]: Starting PVE API Proxy Server...
Mar 31 10:39:30 home systemd[1]: Starting PVE Cluster HA Resource Manager Daemon...
Mar 31 10:39:30 home kernel: [    9.094781] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 31 10:39:30 home kernel: [    9.094846] vmbr0: port 1(enp0s25) entered blocking state
Mar 31 10:39:30 home kernel: [    9.094848] vmbr0: port 1(enp0s25) entered forwarding state
Mar 31 10:39:30 home kernel: [    9.094929] IPv6: ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready
Mar 31 10:39:31 home pve-ha-crm[1330]: starting server
Mar 31 10:39:31 home pve-ha-crm[1330]: status change startup => wait_for_quorum
Mar 31 10:39:31 home systemd[1]: Started PVE Cluster HA Resource Manager Daemon.
Mar 31 10:39:31 home pveproxy[1333]: starting server
Mar 31 10:39:31 home pveproxy[1333]: starting 3 worker(s)

Mar 31 10:39:31 home pveproxy[1333]: worker 1334 started
Mar 31 10:39:31 home pveproxy[1333]: worker 1335 started
Mar 31 10:39:31 home pveproxy[1333]: worker 1336 started
Mar 31 10:39:31 home systemd[1]: Started PVE API Proxy Server.
Mar 31 10:39:31 home systemd[1]: Starting PVE Local HA Resource Manager Daemon...
Mar 31 10:39:31 home systemd[1]: Starting PVE SPICE Proxy Server...
Mar 31 10:39:32 home spiceproxy[1340]: starting server
Mar 31 10:39:32 home spiceproxy[1340]: starting 1 worker(s)
Mar 31 10:39:32 home spiceproxy[1340]: worker 1341 started
Mar 31 10:39:32 home systemd[1]: Started PVE SPICE Proxy Server.
Mar 31 10:39:32 home pve-ha-lrm[1342]: starting server
Mar 31 10:39:32 home pve-ha-lrm[1342]: status change startup => wait_for_agent_lock
Mar 31 10:39:32 home systemd[1]: Started PVE Local HA Resource Manager Daemon.
Mar 31 10:39:32 home systemd[1]: Starting PVE guests...
Mar 31 10:39:32 home pveupdate[1289]: <root@pam> starting task UPID:home:0000054D:0000045C:5E8301C4:aptupdate::root@pam:
Mar 31 10:39:33 home pve-guests[1354]: <root@pam> starting task UPID:home:000006B3:0000049E:5E8301C5:startall::root@pam:
Mar 31 10:39:33 home pve-guests[1354]: <root@pam> end task UPID:home:000006B3:0000049E:5E8301C5:startall::root@pam: OK
Mar 31 10:39:33 home systemd[1]: Started PVE guests.
Mar 31 10:39:33 home systemd[1]: Reached target Multi-User System.
Mar 31 10:39:33 home systemd[1]: Reached target Graphical Interface.
Mar 31 10:39:33 home systemd[1]: Starting Update UTMP about System Runlevel Changes...
Mar 31 10:39:33 home systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Mar 31 10:39:33 home systemd[1]: Started Update UTMP about System Runlevel Changes.
Mar 31 10:39:34 home pveupdate[1357]: update new package list: /var/lib/pve-manager/pkgupdates
Mar 31 10:39:36 home pveupdate[1289]: <root@pam> end task UPID:home:0000054D:0000045C:5E8301C4:aptupdate::root@pam: OK
Mar 31 10:39:36 home systemd[1]: pve-daily-update.service: Succeeded.
Mar 31 10:39:36 home systemd[1]: Started Daily PVE download activities.
Mar 31 10:39:36 home systemd[1]: Startup finished in 12.717s (firmware) + 6.256s (loader) + 2.655s (kernel) + 12.105s (userspace) = 33.734s.
Mar 31 10:39:40 home kernel: [   18.690225] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
Mar 31 10:39:40 home kernel: [   18.895792] FS-Cache: Loaded
Mar 31 10:39:40 home kernel: [   18.913608] FS-Cache: Netfs 'nfs' registered for caching
Mar 31 10:39:40 home kernel: [   19.018211] NFS: Registering the id_resolver key type
Mar 31 10:39:40 home kernel: [   19.018219] Key type id_resolver registered
Mar 31 10:39:40 home kernel: [   19.018220] Key type id_legacy registered
Mar 31 10:39:40 home systemd[1]: /lib/systemd/system/rpc-statd.service:13: PIDFile= references path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingly.
Mar 31 10:39:40 home systemd[1]: Starting Preprocess NFS configuration...
Mar 31 10:39:40 home systemd[1]: Reached target Host and Network Name Lookups.
Mar 31 10:39:40 home systemd[1]: nfs-config.service: Succeeded.
Mar 31 10:39:40 home systemd[1]: Started Preprocess NFS configuration.
Mar 31 10:39:40 home systemd[1]: Starting Notify NFS peers of a restart...
Mar 31 10:39:40 home systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Mar 31 10:39:40 home sm-notify[1774]: Version 1.3.3 starting
Mar 31 10:39:40 home systemd[1]: rpc-statd-notify.service: Succeeded.
Mar 31 10:39:40 home systemd[1]: Started Notify NFS peers of a restart.
Mar 31 10:39:40 home rpc.statd[1776]: Version 1.3.3 starting
Mar 31 10:39:40 home rpc.statd[1776]: Flags: TI-RPC
Mar 31 10:39:40 home systemd[1]: Started NFS status monitor for NFSv2/3 locking..
Mar 31 10:39:55 home systemd[1]: systemd-fsckd.service: Succeeded.
 
Hier noch der Rest:

Code: 
Mar 31 10:39:57 home systemd-timesyncd[810]: Synchronized to time server for the first time [2001:638:504:2000::33]:123 (2.debian.pool.ntp.org).
Mar 31 10:40:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:40:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:40:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:41:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:41:01 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:41:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:42:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:42:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:42:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:42:41 home kernel: [  199.720652] nfs: server 192.168.178.23 not responding, still trying
Mar 31 10:43:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:43:01 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:43:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:44:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:44:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:44:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:44:11 home pvedaemon[1324]: <root@pam> successful auth for user 'root@pam'
Mar 31 10:44:41 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:45:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:45:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:45:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:45:04 home pveproxy[1336]: proxy detected vanished client connection
Mar 31 10:46:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:46:01 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:46:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:47:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:47:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:47:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:47:13 home kernel: [  472.104636] nfs: server 192.168.178.23 not responding, still trying
Mar 31 10:47:36 home kernel: [  494.632645] nfs: server 192.168.178.23 not responding, still trying
Mar 31 10:48:00 home systemd[1]: Starting Proxmox VE replication runner...

Mar 31 10:48:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:48:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:49:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:49:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:49:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:50:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:50:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:50:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:51:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:51:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:51:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:51:28 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:51:28 home pveproxy[1336]: proxy detected vanished client connection
Mar 31 10:51:44 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:51:45 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:51:46 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:51:52 home systemd[1]: Created slice User Slice of UID 0.
Mar 31 10:51:52 home systemd[1]: Starting User Runtime Directory /run/user/0...
Mar 31 10:51:52 home systemd[1]: Started User Runtime Directory /run/user/0.
Mar 31 10:51:52 home systemd[1]: Starting User Manager for UID 0...
Mar 31 10:51:52 home systemd[3205]: Listening on GnuPG network certificate management daemon.
Mar 31 10:51:52 home systemd[3205]: Reached target Timers.
Mar 31 10:51:52 home systemd[3205]: Reached target Paths.
Mar 31 10:51:52 home systemd[3205]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 31 10:51:52 home systemd[3205]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 31 10:51:52 home systemd[3205]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 31 10:51:52 home systemd[3205]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 31 10:51:52 home systemd[3205]: Reached target Sockets.
Mar 31 10:51:52 home systemd[3205]: Reached target Basic System.
Mar 31 10:51:52 home systemd[3205]: Reached target Default.
Mar 31 10:51:52 home systemd[3205]: Startup finished in 42ms.
Mar 31 10:51:52 home systemd[1]: Started User Manager for UID 0.
Mar 31 10:51:52 home systemd[1]: Started Session 1 of user root.
Mar 31 10:51:58 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:52:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:52:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:52:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:52:15 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:52:15 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:52:16 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:52:28 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:52:45 home pveproxy[1334]: proxy detected vanished client connection

Mar 31 10:53:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:53:01 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:53:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:53:15 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:53:15 home pveproxy[1334]: proxy detected vanished client connection
Mar 31 10:53:59 home kernel: [  877.608664] nfs: server 192.168.178.23 not responding, still trying
Mar 31 10:54:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:54:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:54:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:54:52 home systemd[1]: Starting Cleanup of Temporary Directories...
Mar 31 10:54:52 home systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Mar 31 10:54:52 home systemd[1]: Started Cleanup of Temporary Directories.
Mar 31 10:55:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:55:01 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:55:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:56:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:56:01 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:56:01 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:57:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:57:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:57:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:57:30 home pveproxy[1336]: proxy detected vanished client connection
Mar 31 10:58:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:58:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:58:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 10:59:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 10:59:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 10:59:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 11:00:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 11:00:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 11:00:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 11:01:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 11:01:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 11:01:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 11:02:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 11:02:00 home systemd[1]: pvesr.service: Succeeded.
Mar 31 11:02:00 home systemd[1]: Started Proxmox VE replication runner.
Mar 31 11:03:00 home systemd[1]: Starting Proxmox VE replication runner...
Mar 31 11:03:00 home systemd[1]: pvesr.service: Succeeded.
 
offensichtlich wird das NAS (192.168.178.23) nicht erreicht

ping vom Server bringt folgendes:

Code: 
ping 192.168.178.23
PING 192.168.178.23 (192.168.178.23) 56(84) bytes of data.
64 bytes from 192.168.178.23: icmp_seq=1 ttl=64 time=2.29 ms
64 bytes from 192.168.178.23: icmp_seq=2 ttl=64 time=3.40 ms
64 bytes from 192.168.178.23: icmp_seq=3 ttl=64 time=3.46 ms
 
Kann mir denn jemand sagen was die Fragezeichen bedeuten, welche auf dem Bild in Post #1 zu sehen sind?
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back