When using custom HTTPS domains in Salesforce, most Certificate Authorities (CAs) issue certificates with intermediate certificates in the signing chain. If the browser or system connecting to your domain does not have these intermediate certificates installed as trusted, HTTPS connections to your custom domain may fail. Uploading a complete certificate chain — including the domain certificate, all intermediate certificates, and the root certificate — to Salesforce resolves this issue. This approach also addresses the common "certificate verify failed (unable to get local issuer certificate)" error.
Most of the Certificate Authority (CA) now has intermediate certificates. This causes an issue when custom domain and certificates are used in Salesforce. More information on adding custom domains and certificates can be found in the following articles:
Some systems or browsers don't have trusted intermediate certificates. To resolve this, those certificates need to be installed and trusted.
Another solution, in that case, is to upload a certificate chain in salesforce and associate that with custom domain.
Note: Merging a complete certificate change will also help address certificate verify failed (unable to get local issuer certificate) errors.
To resolve certificate chain errors for custom HTTPS domains in Salesforce, create a single certificate chain file by stacking all certificates in the correct order (domain first, then intermediate certificates, then root certificate) and upload it to Salesforce via Setup then Security Controls then Certificate and Key Management.
-----BEGIN CERTIFICATE----- MIIGvTCCBaWgAwIBAgIQBsyeRo2C7ECRbEpmpu+mazANBgkqhkiG9w0BAQUFADBI [TRUNCATE] MDEyMDAwMFowgYcxCzAJBgNVBAYTAlVTMREwDwYDVQQIEwhNYXJ5bGFuZDESMBAG v+PMGxmcJcqnBrJT3yOyzxIZow== -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- MIIEjzCCA3egAwIBAgIQBp4dt3/PHfupevXlyaJANzANBgkqhkiG9w0BAQUFADBh [TRUNCATE] slXkLGtB8L5cRspKKaBIXiDSRf8F3jSvcEuBOeLKB1d8tjHcISnivpcOd5AUUUDh v+PMGxmcJcqnBrJT3yOyzxIZow== -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- MIIDrzCCApegAwIBAgIQCDvgVpBCRrGhdWrJWZHHSjANBgkqhkiG9w0BAQUFADBh [TRUNCATE] CAUw7C29C79Fv1C5qfPrmAESrciIxpg0X40KPMbp1ZWVbd4= -----END CERTIFICATE-----
Error: Certificate's subject distinguished name (DN)
<certificate info> is not equal to the previous certificate's issuer DN <certificate info> 000386535

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.