ovftool fails with curl error: couldn't connect to server

[ffraticelli]

HI,

I'm trying to create an OVF using ovftool 3.0.1. When I issue the ovftool command from the command line I get:

Error: cURL error: Couldn't connect to server
Completed with errors

I used the following command:

/usr/bin/ovftool vi://username:password@XX.XX.XX.XX/datacenter/vm/folder/vmname /destination

I can issue the command as above without the vmname to see if I can access Vsphere and to make sure I have a valid source locator.  The command is successful and returns a list of VMs I can use. When I add the VM name to the source locator path, I get the above error. The VM is pysically about 14GB in size (that is the space alloacted).

I can use the same command to another Vpshere server and I'm successful in creating the OVF. Which leads me to think that it might be a configuration issue with this Vsphere server?

What sorts of issues can lead to the above error?

Thanks,

Fernando

[Chichun]

I got the same problem with you.
The problem was my password hasd special characters.
After changed the password it's work fine.

[StefanAtwork]

Hi,

I find out another workaround. I read the manual and find a solution:

"When you use URIs as locators, you must escape special characters using % followed by their ASCII hex value.
For instance, if you use a "@" in your password, it must be escaped with %40 as in vi://foo:b%40r@hostname,

and a slash in a Windows domain name (\) can be specified as %5c."

Stefan

[mggonzalez]

I'm having the same problem, I don't use any special characters. Any ideas?

[acordova1973]

make sure the VM does not have the CDROM is not using an ISO file

[a_carlos]

No CDROm, no ISO, no special charecters. Have same problem running ovftool in a windows server 2019. 433, 80 e 9089 ports added to firewall excptions. Tested in windows 10 and 11 and works fine. Just windows server 2019 that I got this weird behavour.