Forum Discussion

JYates's avatar
JYates
Community Member
9 days ago

custom domain throws ssl error

Whenever I visit the new domain, I'm getting a name mismatch error. ERR_SSL_UNRECOGNIZED_NAME_ALERT  My DNS looks like this:  learn.reversinglabs.com. 60 IN CNAME learn-reversinglabs.reach360....
reach 360
StevenBenassi's avatar
StevenBenassi
Staff
7 days ago

Hi JYates​,

Sorry to hear that you're having trouble configuring custom domains in Reach 360.

The domain you've shared (learn.reversinglabs.com → CNAME → learn-reversinglabs.reach360.com) is correct DNS-wise, but SSL is failing because the Reach server is presenting a certificate for *.reach360.com. Your browser is requesting learn.reversinglabs.com. Since those don't match, the browser is throwing a name mismatch error.

Reach 360 does not support arbitrary custom domains with customer-provided SSL certificates. That means users cannot upload their own certificates, or use any custom domain and expect SSL to work automatically. SSL should work properly when using the Reach 360-managed domain setup.

When you enable "Use my own domain", Reach provisions an SSL certificate for your specific domain. However, this only works if the domain is properly configured, and the platform has completed domain validation and certification issuance.

Also, you mentioned:

If I switch to “Use my own domain,” will it break the old URL?

Potentially yes, as Reach typically expects one primary domain. Once switched, the old reach360.com URL may redirect or stop being the authorized access point. Currently, there is no officially supported "both URLs function indefinitely" setup. 

One option you can explore is:

  1. Enable “Use my own domain” in Reach 360.
  2. Complete domain setup (DNS + validation)
  3. Let Reach provision SSL.
  4. Keep the old URL temporarily.
  5. Communicate the migration to users.

 

Let me know how it goes!