Page 1 of 1
SSH Connection to Proxmox not using the server adress entered in GUI..
Posted: Tue Feb 10, 2026 1:56 pm
by christoffer1984
Default it looks like when you connect to Proxmox on a different IP/Server address then the host is using HTTP (8006) works.
But SSH doesnt in the logs it tries to connect to the hosts ip adress not what you entered in the server connection.
One option to override this default behaviour similar to this: "use this server address for ssh" would be good.
And should it be possible when you connect to the proxmox host that it checks already then if there is access on the ssh port, simple port open check?
Because now it creates the vm etc before it fails, and it should fail already then in my opinion "SSH not responding".
TLDR:
An option to use the IP/server address you enter to the Proxmox host in the gui, to use that for SSH as well. Not only http (8006).
xx.xx.xx.xx here in the logs is not the Server address i used to connect to Proxmox:
2/10 14:19:21.245 1b8c Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::ConnectSSH: Attempting connection to xx.xx.xx.xx...
2/10 14:19:42.269 1b8c Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::ConnectSSH: Connect failed for xx.xx.xx.xx. WSA=10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
)
2/10 14:19:42.269 1b8c Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::ConnectSSH: TCP connect failed: WSA=10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Re: SSH Connection to Proxmox not using the server adress entered in GUI..
Posted: Tue Feb 10, 2026 2:47 pm
by yaroslav (staff)
Check this build
https://starwind.my.salesforce.com/sfc/ ... XlX0Tfgtsw.
They improved things with ssh logins, I believe.
Re: SSH Connection to Proxmox not using the server adress entered in GUI..
Posted: Tue Feb 10, 2026 5:18 pm
by christoffer1984
I already downloaded that from another thread here in the forums (thats how i could see more details in the logs).
Re: SSH Connection to Proxmox not using the server adress entered in GUI..
Posted: Tue Feb 10, 2026 8:43 pm
by yaroslav (staff)
I have pushed your request to the dev team. Thanks for your suggestions.
Re: SSH Connection to Proxmox not using the server adress entered in GUI..
Posted: Sat Apr 04, 2026 7:40 am
by EmanuelDSterns
The information you shared is very useful, thank you so much!
Re: SSH Connection to Proxmox not using the server adress entered in GUI..
Posted: Wed Jul 15, 2026 3:31 am
by ultimateaffair
Thank you for sharing this helpful information!
Re: SSH Connection to Proxmox not using the server adress entered in GUI..
Posted: Sat Oct 10, 2026 5:16 pm
by excelsi84
Thanks for this 850 Build.
But the issue in this build is that he takes the full size of a Dynamic Hyper-V Disk (which is by default 127 GB) as required for a migration and not the used size of the disk (also if i tick the option "Shrink Size").
Build 848
Code: Select all
10/10 18:44:50.366 1da4 Facility ???INFO: CPPConverting::Convert: Converting VM "pfsense" (1 of 1)
10/10 18:44:50.366 1c3c Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: CreateVM attempt 1/10
10/10 18:44:50.366 1c3c Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Set disks
10/10 18:44:50.366 1c3c Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: disk name scsi0, local-lvm:32.000000,format=raw
10/10 18:44:50.366 1c3c Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace: disk name disk size = 32.000000 Gb
10/10 18:44:50.366 1c3c Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace::<lambda_ff13655038bc08377f040195fc2d064a>::operator (): l
10/10 18:44:50.366 1c3c Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace::<lambda_ff13655038bc08377f040195fc2d064a>::operator (): ......
10/10 18:44:50.366 1c3c Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace: storage is found
Build 850
Code: Select all
10/10 18:55:12.027 1cd4 Facility ???INFO: CPPConverting::Convert: Converting VM "pfsense" (1 of 1)
10/10 18:55:12.027 2aa0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: CreateVM attempt 1/10
10/10 18:55:12.027 2aa0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Set disks
10/10 18:55:12.027 2aa0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: disk name scsi0, local-lvm:127.000000,format=raw
10/10 18:55:12.027 2aa0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace: disk name disk size = 127.000000 Gb
10/10 18:55:12.027 2aa0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace::<lambda_ff13655038bc08377f040195fc2d064a>::operator (): l
10/10 18:55:12.027 2aa0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace::<lambda_ff13655038bc08377f040195fc2d064a>::operator (): .hQ...
10/10 18:55:12.027 2aa0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace: storage is found
10/10 18:55:12.027 2aa0 Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Not enough space
10/10 18:55:12.027 1cd4 Facility ???ERROR: CPPConverting::Convert: FAILED
Re: SSH Connection to Proxmox not using the server adress entered in GUI..
Posted: Sat Oct 10, 2026 7:24 pm
by yaroslav (staff)
Please output it to some intermediate host (i.e., individual disk conversion, not VM).
Please wait for the future builds to come.
Re: SSH Connection to Proxmox not using the server adress entered in GUI..
Posted: Sun Oct 11, 2026 5:42 am
by excelsi84
yaroslav (staff) wrote: ↑Sat Oct 10, 2026 7:24 pm
Please output it to some intermediate host (i.e., individual disk conversion, not VM).
Please wait for the future builds to come.
Thanks.
I tried to convert the disk only, but in the process i have to select/create a vm on the proxmox host, instead of simply select the proxmox storage as target.
There i got following error in comparision to 848:
848 (it created a 32 gb disk)
Code: Select all
10/10 18:45:03.555 1da4 Facility ???INFO: CPPConverting::ConvertDisks: pathInput: E:\VM\hyper\pfSense\Virtual Hard Disks\pfSense.vhdx, pathOutput: /dev/pve/vm-106-disk-0
10/10 18:45:03.596 1da4 Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 1.
10/10 18:45:03.596 1da4 Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 2.
10/10 18:45:03.596 1da4 Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 1.
10/10 18:45:03.596 1da4 Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 2.
10/10 18:45:03.596 1da4 Facility ???INFO: CVHDXFile::ParseFile: Log is empty.
10/10 18:45:03.597 1da4 Facility ???INFO: CVHDXFile::getRegion: Read region header 1.
10/10 18:45:03.597 1da4 Facility ???INFO: CVHDXFile::getRegion: Read region header 1.
10/10 18:45:03.597 1da4 Facility ???INFO: CPPConverting::ConvertDisks: CreateInputImage: 0
10/10 18:45:04.560 1da4 Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::ConnectSSH: sftp_open failed host=192.168.20.22 user=convert path=/dev/pve/vm-106-disk-0 sftp_err=3 session_msg=Failed opening remote file
10/10 18:45:04.561 1da4 Facility ???INFO: CPPConverting::ConvertDisks: CreateOutputImage: 0
10/10 18:45:04.562 1da4 Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::Write: Failed to write to remote file
850
Code: Select all
10/11 7:32:44.721 37f0 Facility ???INFO: CPPConverting::ConvertDisks: pathInput: E:\VM\hyper\pfSense\Virtual Hard Disks\pfSense.vhdx, pathOutput: /dev/pve/vm-105-disk-0
10/11 7:32:44.762 37f0 Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 1.
10/11 7:32:44.762 37f0 Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 2.
10/11 7:32:44.762 37f0 Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 1.
10/11 7:32:44.762 37f0 Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 2.
10/11 7:32:44.762 37f0 Facility ???INFO: CVHDXFile::ParseFile: Log is empty.
10/11 7:32:44.762 37f0 Facility ???INFO: CVHDXFile::getRegion: Read region header 1.
10/11 7:32:44.762 37f0 Facility ???INFO: CVHDXFile::getRegion: Read region header 1.
10/11 7:32:44.763 37f0 Facility ???INFO: CPPConverting::ConvertDisks: CreateInputImage: 0
10/11 7:32:44.790 37f0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::ConnectSSH: Attempting connection to 192.168.20.22...
10/11 7:32:44.792 37f0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::ConnectSSH: Successfully connected to 192.168.20.22
10/11 7:32:46.163 37f0 Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::ConnectSSH: sftp_open failed host=192.168.20.22 user=convert path=/dev/pve/vm-105-disk-0 sftp_err=3 session_msg=Failed opening remote file
10/11 7:32:46.165 37f0 Facility ???ERROR: ProxmoxDisk::CreateOutputImage: Error connecting to disk: ..(.X.
10/11 7:32:46.165 37f0 Facility ???INFO: CPPConverting::ConvertDisks: CreateOutputImage: 1
10/11 7:32:46.165 37f0 Facility ???ERROR: CPPConverting::Convert: FAILED
The VM was created and i also see the 127 gb raw disk file on the proxmox host (the size is the cause of the error i assume, beacause there is not enough space for 127 gb).
SSH login with the conversion user is working.
P.S.: I tried a new conversion with a shrinked hyper-v disk on Build 850 and i got a new error:
Code: Select all
10/14 19:32:50.436 158 Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::ConnectSSH: sftp_open failed host=192.168.20.22 user=convert path=/dev/pve/vm-105-disk-0 sftp_err=3 session_msg=Failed opening remote file
10/14 19:32:50.437 158 Facility ???ERROR: ProxmoxDisk::CreateOutputImage: Error connecting to disk: l5.w.
10/14 19:32:50.437 158 Facility ???INFO: CPPConverting::ConvertDisks: CreateOutputImage: 1
10/14 19:32:50.438 158 Facility ???ERROR: CPPConverting::Convert: FAILED
An intermediate host or location for the disk i dont want to use, i wait for the newer builds.