Unable to deploy ovf-template

[ihateyourprobs]

Hey guys, I need your help

after upgrading from ESXi 4.1 to ESXi 5.1.0 (Build 799733) I'm no longer able to deploy my .ovf-Templates.

When using vSphere Client to do so, I throws an error as "Error reading Data: the remote server is not available (Errorcode 503)".

When trying to browse the datastore from within the webinterface, it does not open the directory and leaves a blank page (and of course not even the https login/password protection appears).

I already tried restarting all management services, but it doesn't helped me anything.

Maybe you can give me some hints, thanks for that in advance.

[zXi_Gamer]

Can you check if you are using the vSphere Client of 5.1's and possibly the latest ones?

[ihateyourprobs]

Sure - I use vSphere Client 5.1 Build 786111

(I don't really think that it is a vsphere client issue as I'm not possible to browse the datastore from the web frontend as well....)

kind regards

[zXi_Gamer · Accepted solution]

Alrighty then.... Lets check the usual suspects:

When using vSphere Client to do so, I throws an error as "Error reading Data: the remote server is not available (Errorcode 503)".

1. Check the firewall settings from the ESX/the client side.

2. Check if the ESXi server dns is resolved and configured properly.

it does not open the directory and leaves a blank page (and of course not even the https login/password protection appears).

3. Can you confirm from a different windows machine to check out the windows tcp/ip bug

[zXi_Gamer]

ihateyourprobs nice nic name when you have probs

[ihateyourprobs]

you think my nick is counterproductive? :smileygrin:

so let's talk about your advices:

- firewall --> "esxcli network firewall ruleset list" shows that "httpclient" is not enabled;  enabled it - works

thank you very very much for helping despite my nickname :smileygrin:

edit/ if someone reads this later - httpclient is not the appropriate ruleset for ovf deploy, only for browsing the datestore from within the webfrontend, if the deployment crashes with 503 remote server unavailable, enable the relevant rulesets (I can only guess - it is remoteSerialPort, gdbserver, vspc or something like that...)

[zXi_Gamer]

thank you very very much for helping despite my nickname :smileygrin:

most welcome

[Lessi001]

edit: just noticed you have already a solution for your problem... forget my suggestion.

Hm, I can remember there was a flaw in the TCP Stack causing error 503... maybe this KB will help you:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=203382...

Regards,

Andi

[ihateyourprobs]

first: problem has been solved as I followed  zXi_gamers advices.

secound: your kb is related to vcenter server

thanks and kind regards

[ihateyourprobs]

Sorry guys,

unfortunately I have to reopen this topic, as it seems not be resolved completely...

From yesterday on, esxi throws the error again despite of changing nothing

"...the remote server returned an error: (503) server unavailable"

Firewall ports are open and I guess everything (actually I don't have to configure anything) ist configured well...

(Yes, I'm able to connect via ssh.)

Can anyone of you guys help me with that???

cheers

[ihateyourprobs]

Anyone any ideas? Pleaaaase ?!

[mmangold]

Add the hosts to the NO_PROXY config to bypass the proxy:

• Connect to the vCenter Server with a SSH session
• Modify the /etc/sysconfig/proxy file and add the ESXi host FQDN's or IP's to the following line, comma-separated. 

         
Example

NO_PROXY="localhost, 127.0.0.1, ESXi-01.test.com,"

• Attempt the OVF deployment from the content library and the vSphere Client.

Note: vCenter 7.0U1c includes support to specify a CIDR notation (1.2.3.4/24)/netmask notation (1.2.3.4/255.255.255.0) or a regex (: .*vmware.com) Please note, regex, not a wildcard.

For example:
NO_PROXY="localhost, 127.0.0.1, .*.vmware.com, 192.168.1.0/24"