Typebot
Log in

Share feedback, ideas and get community help

Updated 3 weeks ago

Custom domain not working - SSL problem

At a glance

The community member set up a custom domain using Infomaniak, but encountered an SSL protocol error. They are unsure if the issue is on Infomaniak's end or if they need to do something else on Typebot. The community members discuss troubleshooting steps, including adding a TXT record and waiting for propagation. Eventually, the community member is able to access the site, but initially encounters a 404 error, which is resolved by including an additional slug in the URL.

Useful resources
UUlrich
·
Hello, i did the setup for a custom domain, using Infomaniak - but it says there is a SSL protocol error. See screenshots; i cannot find what i should do to correct this ?
SSL is activated automatically via let's encrypt on Infomaniak - or is something missing on their end ?
Or should i do something else on Typebot ?
Thanks for your help 🙂
Attachments
SCR-20240105-g0v.png
SCR-20240105-g0g.png
SCR-20240105-g15.png
1
B
U
d
16 comments
BBaptiste
Hi, I'm sending a DM
UUlrich
Thanks Baptiste, i did the TXT and waiting it to propagate, will let you know if it works !
BBaptiste
I see that it's propagated now!
UUlrich
Nice, but on the page https://plastibot.dilemme-plastique.ch/ i have 404
The bot you're looking for doesn't exist
Is there something else to do ?
UUlrich
Or to wait ?
BBaptiste
https://plastibot.dilemme-plastique.ch/experience
UUlrich
Oh so great, thanks !!
UUlrich
forgot that there was an additional slug in the link... my bad !
BBaptiste
No problem my friend 🙂
ddeaah
Hi everyone! 👋
I’m setting up a custom domain for Typebot (chopp.b2bdigital.com.br) using HostGator, and I’ve successfully pointed the CNAME to Typebot. However, I’m facing an SSL error.

I saw a similar issue discussed earlier in this thread, and it looks like @Ulrich lrich and Baptiste managed to solve it. Could you share what steps worked for you? Did you have to add a TXT record or do anything else on Typebot’s side?

Thanks in advance! 🚀
UUlrich
Oh that was a long time ago… I think the solving was done by Baptiste - I don’t remember the details
ddeaah
Hey @Ulrich, thanks for your reply! 😊
Do you happen to remember the TXT record that was added?
bborojopower.
Hi guys, I am having the same problem, could you show the solution please?
UUlrich
I looked into Cloudflare, but did not find this TXT record (i think we erased it). We switched to self hosted Typebot, so we do not need the CNAME from Typebot anymore. Sorry that i cannot provide help here...
ddeaah
Hey Ulrich, I managed to solve it with Cloudflare. Thanks! 😊
ddeaah
Hi! I managed to solve it with Cloudflare. Here’s how I did it:

  1. Changed the SSL/TLS mode in Cloudflare from “Flexible” to “Full” (to avoid redirect loops).
  2. Disabled the Cloudflare proxy (Orange Cloud ☁️) for the CNAME pointing to Typebot (so that Cloudflare doesn’t interfere with SSL).
  3. Checked if the custom domain was properly added in Typebot.
  4. Tested everything after making these changes, and it worked!
Let me know if you need any help! 😊
Add a reply
Sign up and join the conversation on Discord