+ Start a Discussion
MJ Kahn / OpFocusMJ Kahn / OpFocus 

Slotmatching5.salesforce.com - "This connection is untrusted" issue with Community custom domain

I’m about to go live with a Community, and I’ve created a custom domain for it. I’ve created the CNAME entry, and in Salesforce, I configured the Domain and its URL, uploaded a CA-Signed certificate, and added the certificate to the domain, all carefully following the documentation. And I’ve waited several days for everything to propagate. Most of the time, now, when I browse to my custom domain (let’s call it my.abc.com), I see the correct page (the login page), I can log into the Community, and everything is fine.
 
However, for some people, in some browsers, they get a message saying “This connection is untrusted,” like this:

This connection is untrusted

This doesn’t happen for everybody. Most people can use the custom domain just fine, which leads me to believe that the domain and certificate are configured properly. The person who reported this error in Firefox is able to get to the Community just fine using another browser on the same computer on the same network.
 
Telling my Community users to just click “I understand the risks” isn’t an option. Why do some people get this error, and what can I do to prevent it?
 
BalajiRanganathanBalajiRanganathan
this link might help

https://support.mozilla.org/en-US/kb/connection-untrusted-error-message#w_certificate-is-only-valid-for-site-name

A common situation is when the certificate is actually for a different part of the same site. For example, you may have visited https://example.com, but the certificate is for https://www.example.com. In this case, if you access https://www.example.com directly, you should not receive the warning
MJ Kahn / OpFocusMJ Kahn / OpFocus
Thank you for your very prompt reply!

I'll pass this thoguht along to the people who gave me the certificate, but noting that the error details are complaining about slotmatching5.salesforce.com, which is definitely not what the certificate is for, I'm wondering if this is really the issue. Any idea where the slotmatching5.salesforce.com is coming from?