I’m following the below document to set up a custom domain for our help centres but am unable to do so given HTTPS (manual setup) appears to not support our domain’s Cloudflare SSL mode (full strict). HTTPS (quick setup) is not available for our existing account
1 - Does HTTPS (quick setup) support full strict SSL via Cloudflare?
2 - Are we able to have HTTPS (quick setup) enabled for our account retroactively?
https://developers.intercom.com/docs/guides/help-center/custom-domains
Cheers
Russ
Best answer by Shaq Payne
Hey Russ!
I was doing some research and this topic hasn’t come in the Community just yet. But we have this post now, which hopefully brings in some more feedback 🙌. I also haven’t seen this come up often when looking at related conversations. So I wasn’t able to get you feedback on what other users have done here or find a proved workaround.
I can go ahead and submit this feedback to the Product team for their review and consideration. In the meantime you can try to quick set up option with Cloudflare proxy disabled but you still may run into issues with the certificate appearing as invalid. But hopefully it works out for your team!
Let me know what other questions I can clarify here and if it works 😃
+2Hey Russ, Shaq from the Support team here in Chicago 👋! Great questions, I’ve added feedback below.
1 - Does HTTPS (quick setup) support full strict SSL via Cloudflare?
Per our doc here strict SSL is not supported and will result in an error: https://www.intercom.com/help/en/articles/7301427-troubleshooting-custom-domain-set-up-and-https-ssl
2 - Are we able to have HTTPS (quick setup) enabled for our account retroactively?
Would you be able to elaborate on this question more? There doesn’t seem like an option to set up SSL in the past but I could be misunderstanding what you mean. I want to make sure I give you the best response here. Looking forward to your response😄!
Thanks!
Thanks for the response
So we’re in a position where the parent domain/zone we wish to host a custom subdomain within is configured to use the Cloudflare Full (strict) TLS mode, as is best-practice. Not supporting this means we’re left with either having to degrade our security posture, or run a proxy just for Intercom (which I’m somewhat reluctant to have my team do)
Does Intercom not support provisioning Let’s Encrypt certs, or similar, for customers wishing to achieve this? There must be plenty of us in the same situation. It appears as though your “HTTPS (quick setup)” implementation provides a certificate, in which case are we able to just configure a CNAME with the Cloudflare proxy disabled?
Referring to the following statement in this doc, it appears this should be possible:
“Since HTTPS (quick setup) option already provides SSL”
Cheers
Russ
+2Hey Russ!
I was doing some research and this topic hasn’t come in the Community just yet. But we have this post now, which hopefully brings in some more feedback 🙌. I also haven’t seen this come up often when looking at related conversations. So I wasn’t able to get you feedback on what other users have done here or find a proved workaround.
I can go ahead and submit this feedback to the Product team for their review and consideration. In the meantime you can try to quick set up option with Cloudflare proxy disabled but you still may run into issues with the certificate appearing as invalid. But hopefully it works out for your team!
Let me know what other questions I can clarify here and if it works 😃
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
