An administrator has migrated a vCenter Server Appliance from version 5.5 to version 6.x. During the migration, the administrator selected DHCP for the appliance and obtained a hostname from the…

SSL certificates generated during migration are issued to the original hostname obtained via DHCP. When the hostname is changed to a static value, the Subject Name in the certificate no longer matches the appliance identity, causing all vCenter services and components that verify the certificate to fail. Regenerating the SSL certificates ensures they are issued for the new static hostname, restoring secure communication across all services.

Re-registering components to SSO is not required solely due to a hostname change; the primary cause of service failures after a hostname change is the SSL certificate mismatch, not SSO registration state.

Updating /etc/hosts addresses local name resolution only and does not resolve the SSL certificate Subject Name mismatch caused by the hostname change.

Restarting only the vpxd service does not address the underlying invalid SSL certificates, and other dependent services would still fail to authenticate.