VMware Cloud Community
drechsau1
Contributor
Contributor
Jump to solution

Can't upload: Error: Transferring files

Preamble:

2 cells behind F5 load balancer.

vCloud Director 1.5, completely fresh install with new database connected to vCenter 5 using ESXi 4.1U1 servers and vShield 5.

Problem:

When I try to upload files, things fail after about 30 seconds: Error: Transfering files


When watching the network, vCloud Director is issuing the NAT IP address from behind the load balancer for the connection and not the load balancer IP or the proper DNS name to the browser.

So, of course, things fail and I can't upload.

I have the settings for vCloud Director set up with proper DNS names for the vCD portal and console.  I do not have anything inserted into the API field at this time.

What do I need to tickle to resolve this issue?

Reply
0 Kudos
1 Solution

Accepted Solutions
tsugliani
VMware Employee
VMware Employee
Jump to solution

Hi,

That's why it doesn't work, you need to fill up the API box too :slightly_smiling_face: (The api will always answer with it's internal http nic setting otherwise, and the upload process goes through the API)

Please try and confirm it works.

Regards,

View solution in original post

Reply
0 Kudos
9 Replies
tsugliani
VMware Employee
VMware Employee
Jump to solution

Hi,

Did you properly setup the public addresses as a vCloud Admin on the vCD Portal (Administration -> Public Addresses)?

This should fix your issue.

edit :

VCD public URL: https://your.dns.name/cloud/

VCD public console proxy address: yourconsole.dns.name

VCD public REST API base URL: https://your.dns.name/

Regards,

Reply
0 Kudos
drechsau1
Contributor
Contributor
Jump to solution

Yes, as I stated in my original message, there are proper DNS names in the first two boxes and everything else is working.

I have not put anything into the API box as of yet.


Edit:

Added in host part for the API and things all of a sudden worked.

I made no changes to either the VCD public URL or the console proxy address.

was:

Public address: https://portal.domain.com/cloud/

Console address: console.domain.com

API: <empty>

Now:

Public address: https://portal.domain.com/cloud/

Console address: console.domain.com

API: portal.domain.com

And now working.  Hmm..

Reply
0 Kudos
tsugliani
VMware Employee
VMware Employee
Jump to solution

Hi,

That's why it doesn't work, you need to fill up the API box too :slightly_smiling_face: (The api will always answer with it's internal http nic setting otherwise, and the upload process goes through the API)

Please try and confirm it works.

Regards,

Reply
0 Kudos
drechsau1
Contributor
Contributor
Jump to solution

Well, that seemed to take care of things.

Please update the documentation to state such so that others don't have to split hairs trying to figure out what is going on and why.

Thank you very much.

Reply
0 Kudos
tsugliani
VMware Employee
VMware Employee
Jump to solution

This is described in the vCloud Director Administrator's Guide

Page 98 : Configure the Public REST API Base URL.

Regards,

drechsau1
Contributor
Contributor
Jump to solution

I understand that this needs to be set up for the API to function.

Uploading a file where you haven't set up any API calls yourself but requiring that field to be filled in needs to be correctly updated in the documentation.

Or better yet, make the field required instead of optional.

Again, thanks, your clue was what I needed.  I understand, technically, why this needed to be filled in (in hindsight). What may be confusing to others is that the uploader is using the API functionality for the action involved without any knowledge of the end user or the neophyte administrator knowing that it is using the API functionality.

Edit:

you referenced that this data is in the admin guilde for vCloud Director 1.5


Can you tell me which page and paragraph specifically?

Page 98  has some info but not specifically about uploading

Found the paragraph!

(you just replied as well about page 98)

During the initial configuration of each cloud cell, you specified an HTTP service IP address. By default, vCloud Director uses that address in the XML responses from the REST API and as the upload target for the transfer service (for uploading vApp templates and media). To use a different address, specify a public REST API base URL.

Bold area is the data required.

Thank you, an easy to miss item in my opinion.

Reply
0 Kudos
tsugliani
VMware Employee
VMware Employee
Jump to solution

I will send this feedback to the documentation team to see how they can explain/highlight this "unclear" setting in a better way.

aha_tom
Enthusiast
Enthusiast
Jump to solution

Got the same issue. Thanks for the post now its working.

Reply
0 Kudos
alexandremercie
Contributor
Contributor
Jump to solution

During the initial configuration of each cloud cell, you specified an HTTP service IP address. By default, vCloud Director uses that address in the XML responses from the REST API and as the upload target for the transfer service (for uploading vApp templates and media). To use a different address, specify a public REST API base URL.

This is untrue.

By default (public addresses not configured) vCloud Director uses the "host" HTTP header in all XML responses except for the upload target for the transfer service. It uses the HTTP service IP of the cell.

Reply
0 Kudos