Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"vCenter Server Appliance FQDN does not match the certificate in VMware Endpoint Certificate Store" while upgrading from vCenter 6.5/6.7 to 7.0 (78657)

Last Updated: 4/15/2020Categories: TroubleshootingTotal Views: 24263Language:
Chinese (Simplified)JapaneseEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

Upgrade from vCenter 6.5 /6.7 to VCSA 7.0 fails with error:

The vCenter Server Appliance FQDN <FQDN of the vCenter> does not match the certificate in VMware Endpoint Certificate Store

Cause

This issue is caused when:

The error is seen when the arguments are passed to the check (The sso.cert.dnsnames supposed to be comma separated but appears simple concatenation)

Since the DNS entries are concatenated, PNID != DNS name, the failure occurs

Common Name (CN) is same as PNID

Certificates has multiple DNS Entries in SAN

The workflow checks the match with pnid against CN first, if that match fails, then its checked against the DNS entries

Resolution

VMware is aware of this issue.

Currently, there is no resolution.

Workaround

To workaround this issue, use one of these options

Workaround 1

Ensure the Common Name (CN) matches with the PNID while generating the certificates.

OR

Workaround 2

Generate new certificates where both DNS and IP contains only 1 value.

Example: DNS only contains test.domian.com and also CN is also modified to test.domian.com

Replace the Machine SSL Certificate in VCSA 6.7 U3 and perform upgrade to 7.0.

Related Information

"vCenterServer FQDN Source_vCenter_Server_Appliance_FQDN does not match DNS servers" error when upgrading from vCenter Server Appliance 5.x to 6.0

vCenter Server certificate validation error for external solutions in environments with Embedded Platform Services Controller

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
[VMC on AWS] Cloud Assembly で VMware Cloud on AWS のクラウドアカウントを作成できない (78671)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant