VMware Cloud Community
valentino_86xxx
Contributor
Contributor
Jump to solution

SSL Connection Timeout Error

Hi everyone!

I'm trying to convert CentOS 6 VM from Xen 6 to vCenter 5.5 by VMware Converter Standalone 6.2

Everything is ok but the percentage is always 1%. When I opened the log, I got an error:

"error: class Vmacore::Ssl::SSLHandshakeTimeoutException(SSL Exception: Operation was canceled)"

After I try to increase SSLHandshakeTimeout in /etc/vmware/hosts/config.xml and /etc/vmware/rhttpproxy/config/xml from default 20000 miliseconds to 120000 miliseconds, the error is still happened. Somebody help me to fix this error, please!

My log file is attached below

Thank everyone!

1 Solution

Accepted Solutions
POCEH
VMware Employee
VMware Employee
Jump to solution

The advice to use 10.x.x.x is because sysinfo of Linux shows 2 nics and one of them is 10.x.x.x

Otherwise looks like network/proxy issue, connections between source, destination and server machines are described in help, as well as ports required, so try the conversion within "one network".

HTH

View solution in original post

0 Kudos
5 Replies
RickVerstegen
Expert
Expert
Jump to solution

Try again after disabling SSL. The link below describes how you can disable SSL. This will also speeding up the conversion process.
VMware Knowledge Base

Rick

Was I helpful? Give a kudo for appreciation!
Blog: https://rickverstegen84.wordpress.com/
Twitter: https://twitter.com/verstegenrick
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Could you try the conversion with 10.x.x.x source address instead of 192.168.y.y?

valentino_86xxx
Contributor
Contributor
Jump to solution

After disabling SSL I try it again but the error is still happened. Maybe it's not the SSL of Converter, it's the prevention of VMWare infrastructure's SSL (vCenter, ESXi)

0 Kudos
valentino_86xxx
Contributor
Contributor
Jump to solution

Yes,

The source is in my local network (192.168.x.x) and I use the converter installed in Windows 10 to remote access (VPN) to the destination in network (10.x.x.x). I saw my PC IP address has been changed, I can't ping to any but I can telnet, ssh, remote desktop... because all ports are opened.

0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

The advice to use 10.x.x.x is because sysinfo of Linux shows 2 nics and one of them is 10.x.x.x

Otherwise looks like network/proxy issue, connections between source, destination and server machines are described in help, as well as ports required, so try the conversion within "one network".

HTH

0 Kudos