<

HOW TO: Fix VMware vCenter 7.0 Resolving the HTTP 500 Internal Server Error in HA Mode

Posted on
10,553 Points
1,554 Views
Last Modified:
Published
Experience Level: Beginner
28:16
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
EE Fellow, MVE, Expert of the Year 2021,2017-11, Scribe 2016-2012, Author of the Year 2018-6,2013-2012 VMware vExpert Pro, vExpert 2025-2011
I recently returned to the VMware vSphere Server 7.0 EE-Lab to start exploring and creating content around VMware Cloud Foundation. The lab features some powerful DELL R720 and R730 servers, perfect for delving into VMware Cloud Foundation.

After several months away from the EE-Lab, I attempted to access the VMware vCenter Server 7.0, only to be greeted with the dreaded:

HTTP Status 500 - Internal Server Error

There are two possible reasons for this error

  1. Certificate  Expiration
  2. Storage on /storage is 95% or less

Unfortunately Certificate Manager is not supported on run on vCenter HA, so this requires one of the nodes to be made active, and the destruction of vCenter HA before we can run Certificate Manager .

Check the video and commands used I've highlighted in the steps below for troubleshooting

In this video, I’ll walk you through the steps to repair and restore the vCenter Server 7.0, which is running in High Availability (HA) mode, and share some helpful tips and tricks along the way.

Other videos I have published in this video

Part 43: HOW TO: Reset vCenter Server 8.0 root and Administrator@vsphere.local passwords

Part 45. HOW TO: Create a new Distributed and VMKernel Portgroups on a VMware vSphere Distributed Switch for the vSphere Cluster for use with vCenter Server HA

Part 46. HOW TO: Create, Configure and Deploy VMware vCenter Server High Availability (HA)

Video Steps

1. Reset the root lockout

use the command

pam_tally2 -–user=root --reset

Open in new window


2. Check /storage on vCenter Server appliance

use the command

df -h 

Open in new window


to check if /storage is above 95%

3. Check certificates

use the following min-script to check if certificates have expired

for store in $(/usr/lib/vmware-vmafd/bin/vecs-cli store list | grep -v TRUSTED_ROOT_CRLS); do echo "[*] Store :" $store; /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store $store --text | grep -ie "Alias" -ie "Not After";done;

Open in new window


Go to Step 7, if you are running vCenter Server HA, you got some more configuration to go throw, so go to step 8.

4. Check vCenter Server build version

use the command

vpxd -v

Open in new window


5. Check vCenter Server uptime

use the command

uptime

Open in new window


6. Check vCenter Server services

use the command

service-control --status --all

Open in new window


7. if you find you have expired certificates from

use the command

/usr/lib/vmware-vmca/bin/certificate-manager 

Open in new window


Select option 8.

8. if using vCenter Server HA you will need to destroy the cluster

use the command

 vcha-reset-primary 

Open in new window


 vcha-destroy -f

Open in new window


9. forgotten Administrator@vsphere.local password ?

use the command

 /usr/lib/vmware-vmdir/bin/vdcadmintool 

Open in new window


0
0 Comments
In an organization, selecting a backup and recovery product can be a complicated task. This gives an opinion and a process that I use and hope that others find helpful.
Effective resource naming conventions are essential in Azure environments. Proper naming makes it easier to manage, monitor, and secure resources, helping teams stay organized as environments grow in complexity.