#SSL issue for Professional Plan with Custom sub-domain

1 messages · Page 1 of 1 (latest)

static loom
#

Hello,
I am encountering an issue following the use of a custom domain for one of our hubs. After the setup, the redirection from our domain name live.sogelife-megaverse.com to the desired hub is working correctly; however, a certificate issue seems to arise. The process I followed is the one described in the documentation: https://hubs.mozilla.com/docs/setup-custom-domain.html#updating-your-custom-domain
Here is the command i used :
curl -X PATCH -H "turkeyauthtoken:{myToken}" "https://3641311c7f.us2.myhubs.net/api/ita/custom-domain?to_domain=live.sogelife-megaverse.com"
I'm using a domain name on AWS and have configured my hosted zone to redirect my domain to the hub's link.

Is it possible to get some assistance to resolve this issue?

wary owl
#

Hello @static loom, have you pointed your cname record to lb.us1.myhubs.net?

The documentation on this has changed

static loom
wary owl
#

We are still ironing out some issues, but we believe that configuring the cname record to point to lb.us1.myhubs.net should fix the issue. Let's see if it changes in the next 30 minutes

#

Do you still have your custom domain connected?

static loom
#

Ok i'll wait a bit. But previously the redirection was working if we ignore the certificate and now we have a 404 not found error while accessing the domain

wary owl
wary owl
#

@static loom I've done some digging and I believe this is an error with our documentation.

You should have set you cname record to point to lb.us2.myhubs.net instead of lb.us1.myhubs.net. Can you attempt to change and see if this fixes the issue?

I have also opened a pull request to correct the documentation. Apologies for this error on our end: https://github.com/MozillaReality/hubs-docs/pull/184

GitHub

Adjusting the documentation to properly represent the cname record requirements

static loom
#

It worked perfectly in our case. Thank you so much for your help.

wary owl
#

Fantastic news!

daring condor
#

That worked for me as well. @wary owl your update to the documentation is still pending.
One thing to add - it would be great to see the custom domain reflected in the admin dashboard. all the links are broken on my end after the custom domain update.

foggy heath
#

Hi, I have a follow up question on this SSL issue, i'm using a domain name registered not on AWS, have used the CNAME to redirect to lb.us1.myhubs.net and am getting the site but with the SSL error 'your connection is not private' What should I use, lb.us1.myhubs.net or lb.us2.myhubs.net, my hubs is on .us1.myhubs.net hope you can help me

foggy heath
#

ok, went for lunch and when i came back it works with SSL, is there a delay on that or something? Seems to be good to know in the future 🙂

wary owl