create storage failed with error 500

[andre78]

Hi,

I do have 4 Proxmox servers and 1 Proxmox Backup server running. (Versions: 8.1-10; 3.1-5)

3 of those machine are in the same LAN as the Backup server and have been working without issues for more than a year. I recently installed Proxmox also on one of my hosted servers. In order to connect it to the backup server, I included both into Netbird. (Netbird is a wireguard-based mesh VPN, similar to tailscale).
This setup was running fine for a week or two, when suddenly the hosted server as well as one of the local servers couldn't connect to the backup server anymore. The onyl change I remember is activating "quantum-safe" encryption, but this change hasn't affected anything else.

That one local server is in the same IP range with a similar setup as those two which are still working fine. Now I cannot connect those that have lost their connection back to the PBs:



The screenshot is for a connection via Netbird, however I am seeing the same result on the local server connecting to the "native" PBS IP address. And this doesn't make sense, as the local machines have identical network setup, only the last octet of the IP is different between those that work and the one that doesn't.

Both problematic hosts can ping the PBS, via local LAN as well as via Netbird. The PBS is listening on all interfaces:



Tailing the logs in /var/log/proxmox-backup/ only shows activity regarding the working hosts, when I try to connect nothing happens in the logs.

How can I further troubleshoot this? I find it especially confusing that adding the PBS in Proxmox via the local network brings up this error. Rebooted, updated everything, and so on.

Thank you!

 

[Chris]

Hi,
if you can ping the PBS host from the PVE hosts, that indicates that the network layer is fine. So you should double check if there are some firewall rules either blocking the hosts on that port or routing your packets incorrectly. You might want to try to use nmap to scan for open port 8007 from the PVE host and check the output of iptables-save.

The onyl change I remember is activating "quantum-safe" encryption, but this change hasn't affected anything else.

Switching the tunneled traffic to some (probably) lattice based encryption algorithm should not affect the connectivity if implemented correctly: as you said you can ping the host, but nevertheless you might switch back to the previous state to exclude this.