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

"Certificate differs from the expected one." error when pairing cloud sites in vCloud Availability 3.5 (78209)

Last Updated: 3/20/2020Categories: TroubleshootingTotal Views: 8042Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When pairing two cloud sites, you see a similar error in the Sites view of the vCloud Availability Provider Portal in both sites:

Certificate differs from the expected one.

In the Sites view of the vCloud Availability Provider Portal, authenticating with the remote site fails.

In /opt/vmware/h4/cloud/log/cloud.log on the vApp Replication Manager, you see a similar entry:

2020-03-10 17:58:58.488 DEBUG - [UI-134bc817-040c-4a75-a5ec-a8e4855b90cd-A9] [job-7] com.vmware.h4.jobengine.JobExecution     : Task 2568a221-3c8f-4650-ada3-bb0cb30f81a4 (WorkflowInfo{type='pair', resourceType='site', resourceId='Site2', isPrivate=false, resourceName=''}) completed with result VcloudSiteInfo{isLocal=false, state=PeerState{incomingCommError=null, outgoingCommError=ApiError{code='CertificateMismatch', msg='Certificate differs from the expected one.', args=[], stacktrace='com.vmware.exception.CertificateMismatchException: Certificate seen on the network differs from the certificate we expected
at com.vmware.exception.converter.ClientExceptionConverter.convertException(ClientExceptionConverter.java:62)
at com.vmware.rest.client.AbstractRestClient.genericExchange(AbstractRestClient.java:151)
at com.vmware.rest.client.json.RestClient.exchange(RestClient.java:97)
...
Caused by: java.security.cert.CertificateException: Certificate seen on the network differs from the certificate we expected
at com.vmware.rest.client.security.ShaTrustManager.checkServerTrusted(ShaTrustManager.java:53)
at java.base/sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:1510)
at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:629)
... 46 more
'}}, apiPublicUrl='https://vcav-site.corp.org', apiVersion='null', site='Site2', description='', apiUrl='https://vcav-site.corp.org', apiThumbprint='SHA-256:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA'}

This issue can occur if one or both of the public API endpoints used to pair the sites use port 443.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs when the public API endpoint port is not explicitly set during pairing as vCloud Availability does not default to using port 443 for the public endpoints while pairing sites.

Resolution

To resolve this issue, ensure that the public API enpoint in each site explicity states the port to be used and when pairing sites, the endpoint URL includes the port information.

In a browser, log into the vCloud Availability Provider Portal of the first site.

In the left pane, click Configuration.

Under Service endpoints > Public API endpoint, ensure the URL contains a port number.

Repeat steps 1-3 for the second site.

Pair the sites as per the Pair Cloud Sites section of the vCloud Availability documentation.

Note: When entering the endpont URL, you much specify the address and port number for the remote site.

Related Information

Similar symptoms can occur due to administrative API session restrictions. For more information, see "Authentication required" error when pairing cloud sites in vCloud Availability 3.x.

For more information on how to pair sites, see the Pair Cloud Sites section of the vCloud Availability documentation.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
「AMQP ブローカ接続のテスト：失敗 - ACCESS_REFUSED - 認証メカニズム PLAIN を使用したログインが拒否されました。詳細については、ブローカのログ ファイルを参照してください。(Test AMQP Broker Connection: Failed - ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.)」 (76149)

KB
•
vSphere コンソールからの vRealize Operations Manager ノードへのアクセス (78377)

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 vCloud Availability

Related Versions:

VMware vCloud Availability 3.5.x

Take Our Survey

Support Assistant