So I’ve been trying to restore a VM to my Proxmox cluster and I keep getting an error `Failed to reach the hypervisor. Error output: can’t open ‘ssh-public-key-string’ - File name too Long`. I tried recreating the workers, testing the connections and rechecking all the configs I can think of and I can’t get past this point. Every host is configured with IP and ‘root’ credentials. Each is available and the workers start up seemingly fine.
Running ‘Veeam Backup and Replication 12 Build : 12.3.2.3617` on Windows Server 2022 Standard
I’ve gone though that while troubleshooting. Everything is via ip, on the same vlan/network. Using the root account as well because I haven’t felt like dealing with the issues around non-root accounts for PVE backup yet. The oddest thing is that the errors don’t even point to an issue. It’s like the connection string is trying to used the ssh public key string in the file creation string which is nonsensical.
I will suggest you take a look at the log to pinpoint the root issue and not just focus on the error output (message).
I’m not seeing much when attempting to search for this error. You can try and view the log file in: C:\ProgramData\Veeam\Backup & Replication\<restore>.log
But your best bet is really to get in touch with Support. Someone may chime in who’ve had this issue before. But, Veeam support for Proxmox is so new..you may not get any relevant responses.
I’ve gone though that while troubleshooting. Everything is via ip, on the same vlan/network. Using the root account as well because I haven’t felt like dealing with the issues around non-root accounts for PVE backup yet. The oddest thing is that the errors don’t even point to an issue. It’s like the connection string is trying to used the ssh public key string in the file creation string which is nonsensical.
I’ve gone though that while troubleshooting. Everything is via ip, on the same vlan/network. Using the root account as well because I haven’t felt like dealing with the issues around non-root accounts for PVE backup yet. The oddest thing is that the errors don’t even point to an issue. It’s like the connection string is trying to used the ssh public key string in the file creation string which is nonsensical.
I will suggest you take a look at the log to pinpoint the root issue and not just focus on the error output (message).
As Shane mentioned, we cannot “replace” Veeam support within the community but it could be very helpful if you could post the solution as soon as the support shared details - would be the best to get in touch with Veeam support.
