OPERATIONAL DEFECT DATABASE
...
...
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. 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x00007fb7d00200a0] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)
This article provides insights and troubleshooting steps when you encountered this error while logging in and accessing the vCenter Server using your vSphere Web Client.
This issue may occur due to a number of reasons such as: The vCenter Server currently down because of maintenance.The reverse Proxy service on vCenter Server is down.The vSphere web client service is down.Mis-configured Firewall settings. Notes: This mis-configuration can only occur on a Windows installation of vCenter Server. A VCSA installation can only have this problem if deliberate changes were made to firewall settings.
Managing the vCenter Server or vCenter Server appliance fails.
Before troubleshooting, it is critical to understand what a "503 Service Unavailable" error is.For more insights, see List of HTTP Status Codes 503 Service Unavailable Flow Chart Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. The inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.A 503 Service Unavailable error is an HTTP response status code that indicates that the server is temporarily unable to handle your request. This can be due to a number of reasons already mentioned in the cause section.There are also different looking 503 pages on other websites:For example: 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x00007fb7d00200a0] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)503 ErrorService Unavailable – DNS FailureHTTP Error 503HTTP 503503 Service Temporarily Available An important thing to remember is that a 503 error is a server-side error. This means that the problem exists within the vCenter Server or website (server) you are trying to access, and not your computer (client). Troubleshooting HTTP response status code "503" on the vSphere Web Client when connecting to the vCenter Server. Try again in a few minutes. Note: it is most likely that the vCenter Server is just busy acknowledging your request. The vCenter server was able to process your request and was able to respond back with the "503 Service Unavailable" error. It is just not able to acknowledge your request either because it is busy with other tasks at the moment or it currently down with very limited services due to maintenance.Try again in a few minutes on a different client. Confirm if you are still get the same error.Confirm the status of the VMware vCenter Services. Ensure all required services are up, running and functional for both the vCenter Server device and any external Platform Services Controller (PSC) device also. For more insights, see: vCenter Server Component and ServicesFirstboot Failed during Install, Deployment, Upgrade, or Migration in vCenter Server and vCenter Server Appliance 6.7vCenter Services on Windows vCenter Server might fail to start due to insufficient permissions for service accounts, refer to KB Error "Logon failure: the user has not been granted the requested logon type at this computer" in vCenter Server for more informationHow to Stop, Start or Restart vCenter Server 6.x ServicesStopping, Starting or Restarting VMware vCenter Server Appliance 6.x & above services Check if there are disk space issues on the vCenter Server or the vCenter Server Appliance. Notes: Disk space issues can cause more than one service to shutdown which can result in the HTTP 503 Error Response Code. Disk space issues do not directly cause a 503 Error Response Code, but the services being down due to a failure causes the error. For vCenter Server Appliance, see: vCenter Server Appliance disk space is fullFor Windows, check task manager and computer disk space. Check whether certificates are expired. Checking Expiration of STS Certificate on vCenter ServerCheck and resolve expired vCenter Server certificates from command line Other causes of critical services being down can include: Database server disconnected for Windows vCenter Server, due to: database service account password changenetwork change Database corruptionMachine account password problems per "invalid credentials LDAP Error Code 49" error when starting Inventory Services in vCenter Server 6.xVery high storage communication latencyVery high virtual CPU contentionTime synchronization problems between vCenter and PSCbetween vCenter and database serverbetween vCenter and ESXi hostsbetween vCenter and domain controllers From the vCenter Server, investigate the vsphere_client_virgo.log file located at:Windows vCenter Server - C:\ProgamData\VMware\vCenterServer\logs\vsphere-client\logs\vCenter Server Appliance - /var/log/vmware/vsphere-client/logs/Also, look at the vpxd.log file located at:Windows vCenter Server: C:\ProgramData\VMware\vCenterServer\logs\vmware-vpxvCenter Server Appliance: /var/log/vmware/vpxd For more insights on Troubleshooting VMware vCenter Server, the vSphere Web Client, Storage and Networking, see the VMware vSphere Troubleshooting Guide. For Troubleshooting Work Flow, see:
vmware-vpxd service on VCSA fails with the error "contains unexpected zero page at block" on vpxd.log (50113962)Accessing the ESXi host through the Host Client UI fails with error: "503 Service Unavailable" (2144962)"invalid credentials LDAP Error 49" error when starting Inventory Services in vCenter Server 6.x (2147280)How to reset the lost or forgotten root password in vCenter Server Appliance 6.5 (2147144) VMware strongly recommends on following Performance Best Practices on VMware vSphere 6.x/7.x VMware vSphere 6.0VMware vSphere 6.5VMware vSphere 6.7VMware vSphere 7.0
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
