vCenter Server Appliance 6.0 : 503 Service Unavailable

Related searches

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x7fc8bad2f810] _serverNamespace = /vsphere-client _isRedirect = false _port = 9090)

This is the error i'm constantly getting when trying to connect to the vCenter Server Web Client.

Details :
  • I'v installed the vCS Appliance 6.0 on an ESXi 6.0 host. It's running on top of it along other VMs.
  • I can access the vCS appliance thourght an SSH client, but every attempt to access the web client ends with the error above.
  • I'v found that causes for this error are: the server being overloaded or under maintenance. However, I'm the only one to have access to this platform.

Any ideas ?

EDIT: Solved

I had a copy of the current vCenter appliance stored on the same ESXi. This created an IP conflict. I changed the IP address of the backup before its creation and the problem was solved

I found the answer:

The problem was that I made a backup of the current vCenter appliance and stored it on the ESXi 6.0 without changing it's IP address. This created an access conflict. All I had to do is to change the IP address of the backup during its creation and the problem was solved

"503 service unavailable" error when connecting to the vCenter , 503 Service Unavailable (Failed to connect to endpoint: Stopping, Starting or Restarting VMware vCenter Server Appliance 6.x services. 4. Thankx @erkfel. I'v figured the problem a while ago: I made a backup of the current vCenter appliance and stored it on the ESXi 6.0 without changing it's IP address. This created an access conflict. All I had to do is to change the IP address of the backup during its creation and Hop it's solved – mdahhani Jul 15 '15 at 13:04

I was getting that 503 error, but my case was a little different:

I changed the IP address of my VCSA 6.0 Update 2 plus its default gateway via the GUI (https://x.x.x.x:5480).

I was able to ping it and ssh into it afterwards, but I was not able to login using either the old (thick) client or the web client. Both were giving me the 503 Server error.

I tried rebooting, but nothing.

After the reboot, I SSHd into it and was able to see that the web client service was not running. The vpxd service was running though. So I started it:

vcsa6:~ # service vsphere-client status
VMware vSphere Web Client is not running.

vcsa6:~ # service vmware-vpxd  status
vmware-vpxd is running

vcsa6:~ # service vsphere-client start
Last login: Sat Dec 10 23:40:00 UTC 2016 on console
Starting VMware vSphere Web Client...
Waiting for VMware vSphere Web Client......
running: PID:22433

vcsa6:~ # service vsphere-client status
VMware vSphere Web Client is running: PID:22433, Wrapper:STARTED, Java:STARTED

I was still getting the 503.

I found then this link, which basically told me to edit the /etc/hosts file of the VCSA and voila: the VCSA FQDN entry in there was still pointing to the old IP address. I changed it and rebooted and now both clients, web and thick, work as before.

503 Service Unavailable (Failed to connect to e |VMware , Error Message: 503 Service Unavailable (Failed to connect to Hi, you need to just restart vmware WebClient service from vcenter server and wait for 8 a) a way to fix this, short of rebuilding the VCSA appliance (did that This issue consistently bit me on 4 fresh builds, and once on upgrade from 6.0U2. Logging in to the vCenter Server or vCenter Server appliance (VCSA) using the vSphere Web Client fails. Accessing the vCenter Server or vCenter Server appliance using the vSphere Web Client fails. You see these errors similar to: 503 Service Unavailable.

I had 503 error issues on my lab/test vCenter 6.0 Update 1. I installed the integrated VCSA on a host that has limited memory, so I dropped the default 8G RAM and multiple CPU to 1 CPU and 4G. I would not go below those and use the default values if you can as webclient 503 errors occur and inventory service connection issues arise without the required RAM. I experienced no issues on the fat client.

Quick Fix: VCSA 503 Service Unavailable Error, I've had this error pop up fairly regularly since deploying my homelab's vCenter Server Appliance as a version 6.5 GA instance and for the most� Reboot VCenter and resolved. Appeared to Drift by about 6 minutes over a couple of months. VMware KB: The VMware VirtualCenter Server service fails to start on the VMware vCenter Server Appliance 6.0 and rep… Vcenter 6 - 503 Service Unavailable

I've solved it with:

/etc/init.d/vpxa restart

Then I had some problems with hostd.

/etc/init.d/hostd restart

It worked great after.

ESXi 6.5 here.

vCenter Server error 503 Service unavailable (failed to connect to , 503 Service unavailable(failed to connect to Endpoint:[class Advanced Troubleshooting of Duration: 7:27 Posted: Apr 29, 2019 Troubleshooting vCenter error: 503 Service unavailable failed to connect to endpoint vpxd webserver pipe Deploying a VMware vCenter Server Appliance (VCSA

check to see if the vmware-vpxd is not stopped. If it is, start it.

-Putty into vcenter (VCSA)-

There was a vCenter 5.5 appliance previously, the hosts were disconnected and the appliance has been deleted as it will not work with 6.0 hosts. There is are two esxi 5.5 hosts and two 6.0 hosts currently, vCenter runs on its own 6.0 host as an appliance.

Once everything rebooted all the services started up and I had a functional vCenter again which was a relief given I was about five minutes away from a restore or a complete rebuild…and ain’t nobody got time for that!

1. You have just updated vCenter (in my case, VCenter Appliance with PSC 6.0 to 6.0U2) 2. You have restarted vCenter, waited for ~ 10 minutes and trying to open web sphere client 3. Unfortunately,e…

We have a vCenter Server appliance (6.0.0.20000 Build 3634791). All was running fine until we shut down the appliance (cleanly) for a planned power outage. Since it came back up, it is no longer possible to access it either with the vCenter Web Client or the vSphere Client. There have been no other changes made. The vSphere Client reports:

Comments
  • A few troubleshooting notes, since you have SSH access you can (1) check the status of the Web Client "service vsphere-client status", you can run it manually if it's not running for some reason (2) you can check the detailed Web Client logs at /var/log/vmware/vsphere-client/, they might contain more info about the issue
  • Thankx @erkfel. I'v figured the problem a while ago: I made a backup of the current vCenter appliance and stored it on the ESXi 6.0 without changing it's IP address. This created an access conflict. All I had to do is to change the IP address of the backup during its creation and Hop it's solved
  • Would you mind putting the information on how you solved this into an "Answer" then marking it as such? That would be very helpful for the StackOverflow site :-)
  • Please do elaborate your answer too.