vCenter Server Appliance (VCSA) Failed to send http data error

When trying to upgrade the vCenter Server Appliance (VCSA) to version 6.7 using the GUI wizard, I’ve got the following error:

 

 

Failed to send http data.

I checked the logs but didn’t find any clue. When installing the VCSA using the CLI I’ve got the same “Failed to send http data” error (link).  The FQDN of the ESXi host was revolvable by DNS and reverse lookup worked.  After changing the ESXi FQDN to the IP address of the ESXi  host, the deployment finished without errors. I changed the “ESXi host or vCenter Server name” in the wizard step 3 and 4 to fix the problem.

I couldn’t find  what causes the “Failed to send http data” error. I had this error during installs and upgrades in different environments. Hopefully someone can explain what happen or it is a bug that will be solved in future releases.

Related posts:

  1. Is the vCenter Server Appliance (VCSA) 5.5 a replacement for the Windows vCenter Server?
  2. What about the VMware vCenter Server Appliance (VCSA) version 5.1?
  3. vCenter Server Appliance (vCSA) automated/unattended deployment
  4. What’s new in the vCenter Server Appliance (vCSA) 6.0
  5. Update the vCenter Server Appliance (VCSA) without internet

7 thoughts on “vCenter Server Appliance (VCSA) Failed to send http data error”

  1. I’m having the same issue in my homelab. DNS forward and reverse resolving has been configured correctly but if I use the FQDN of the target host I’m receiving the same error message. When I use the IP address instead it works fine. Unfortunately I cannot explain either why this happens.

  2. Issue does still persist, even if you give the IP of the host and not the DNS name. Deploying on vCSA 6.7U1 on ESXi 6.7U1. It is not working. Tried on different machines. It has nothing to do with the DNS. Sometimes deployment starts and stops at 20%. Issue is reproduceable.

  3. Same problem here…. we use the poor man solution… we add an entry in c:\windows\drives\etc\hosts the IP and Short/long FQDNS of the VCSA on the client which is used for the installation.

  4. This happens if you are deploying from a machine outside of the target FQDN domain, where the machine is able to resolve the FQDN, but not the short name.

    Example:
    vcsa.fqdn.local <= can resolve
    vcsa <= cannot resolve

    To make the VCSA deployment work, do the following;

    Windows:
    Edit your TCP/IP settings and add the DNS suffix of your domain to the network connection.

    Linux:
    Edit your "/etc/resolv.conf" by adding the following line: "search FQDN.local"

  5. Hi Robert can you please guide me on the below

    Edit your TCP/IP settings and add the DNS suffix of your domain to the network connection.

  6. I ran into this same problem when trying to install VCenter SA from a computer with 2 NICs. One NIC was connected to my ESXI host network, the other NIC was connected to a different network. Once physically disconnected the other NIC, the installer worked as expected.

Leave a Comment