etc/pve/ is just a file system representation of the cluster database, which is located under the path /var/lib/pve-cluster/config.db.

Exclude the /etc/pve/ directory from backup.

Ensure that every Proxmox VE cluster node can correctly resolve other cluster nodes using DNS or the Hosts file.

Consequently, the Proxmox VE backup fails.

This error occurs after a VM has been migrated to another cluster node. Proxmox VE backup failed with Error connecting to proxmox System: '('Connection aborted.', gaierror(-2, 'Name or service not known'))'].VM/Container Backup Proxmox VE backup failed with a connection error For more details how to correctly configure the client name, see Proxmox VE Backup: Adding the Proxmox server (and nodes) to the SEP sesam environment. This problem can only be solved by correctly configuring the Proxmox clients in the SEP sesam environment.If the node added to the SEP sesam environment is not set up correctly and an IP address is used as the client name instead of the client's hostname matching the hostname returned by the Proxmox server, the backup fails.Proxmox VE backup does not work with the client name as plain IP address If vim is not working and you get “Command not found”, try nano instead.See also: Analyzing SEP sesam Log Files – Proxmox VE Backup – Proxmox VE RestoreĬheck FAQ to find the answers to most common questions. Note, this will not persist through a reboot as this is done within the “live image”, so don’t reboot in this process until Proxmox has completely installed.ĮDIT: It seems vim may no longer be part of the installer in 6.3. This should start the Proxmox installer and everything else is smooth sailing.

$ vim /etc/X11/nf # update Driver 'amdgpu'-> 'fbdev' <-be sure to get all instances in the case of a multi-head card which tripped me up initially. What to do? Run the following: $ chmod 1777 /tmp While digging through the logs I noticed that the installer was failing trying to start the X server for the GUI. The bad is that the Proxmox installer fails and dumps out to a command prompt after obtaining a DHCP lease. Fortunately, it has a Ryzen 4700U and should smoke my Pi4 and older Intel 4200U Proxmox box. I was lucky enough to get my hands on one of the new Asus PN50 Ryzen 7 boxes yesterday.

Proxmox installation aborted