Cant login to proxmox from Windows 7

[tim.mothery]

Hello;

I'm attempting to do a V2V migration from a cloud vm to a newly setup Proxmox VE box. I have successfully migrated a Win 10 vm, but any Win 7 (yes I still need to run some Win 7 pro servers) fails to login to proxmox. I thought it might be a self signed cert issue but it can login to an Esxi box which also has a self singed certs.

Any help would be greatly apreciated.
Thanks,
Tim

[yaroslav (staff)]

Welcome to StarWind Forum. The issue is between Proxmox and Windows 7.
If it is a VM try converting it as V2V fro another VM that can talk to hypervisor. If that'sa physical machine, use somethig like disk2VHD and then convert thst disk to Proxmox.
As a workaround, check this out https://www.reddit.com/r/Proxmox/s/mQp2vEeR9z.

[vimusicapk]

Windows 7 lacks modern security protocols like TLS 1.2+ that Proxmox requires. Update your browser or enable TLS 1.2 in Windows 7, or access Proxmox from a newer operating system.

[yaroslav (staff)]

Thanks for the hint.

[tim.mothery]

Thank you both for the help.

The source Win7 VM is with a cloud provider so I don't have access to a 'recovery' environment or access to the hosting hypervisor. This is why I was trying to use P2V from within Win7. I did see the hint about Win7 not having TLS 1.2 and did try a registry hac but it made no difference. I do have access to a standalone Esxi box so I'll P2V it there and then I'll have access to grab the disk image files.

Tim.

[yaroslav (staff)]

You are welcome. Good luck with your project and Happy New Year!

[vimusicapk]

If you're unable to log in to Proxmox from Windows 7, try the following steps:

1. **Check Network Connection**: Ensure your Windows 7 machine can reach the Proxmox server.
2. **Browser Compatibility**: Use a supported browser (like Chrome or Firefox). Internet Explorer may not work properly with Proxmox.
3. **Clear Browser Cache**: Sometimes old cached data can cause login issues.
4. **Correct Login Credentials**: Double-check the username and password.
5. **Firewall**: Ensure your firewall is not blocking access to Proxmox's web interface (default port: 8006).
6. **HTTPS Issues**: If you're using HTTPS, ensure that your browser accepts the self-signed SSL certificate or use HTTP (not recommended for production).

If the problem persists, check the Proxmox server logs for more details.

[bekeanloinse56]

I ran into a very similar issue trying to migrate an old Win7 VM to Proxmox — you're definitely not alone there. In my case, the TLS 1.2 registry hack didn’t help either, and IE was completely useless with the Proxmox web UI.
What finally worked for me was doing exactly what you mentioned — I spun up a standalone ESXi box I had lying around, did a P2V there (used the StarWind V2V tool to convert the disk), and once I had the VMDK, I just transferred it to Proxmox and converted it to QCOW2 with qemu-img.