Streaming live at 10am (PST)

SSL & Domain Issues

I have come across an issue recently with SSL and dealing with e-commerce and root domains

so for many clients having http://domain.com and http://www.domain.com is pretty standard however because of the way the SSL is set up we cannot validate the root domain when using stripe, the only option was to reroute through cloudflair to allow CNAME flattening, however there is then a new issue in that when the SSL renews it’s no longer valid on cloudflair, and setting flexible creates a loop because webflow redirects http to https.

This seems quite critical and wondered what a solution could be because apple pay just doesn’t work and stripe has issues also. I hope this makes sense as a non dev.


Here is my site Read-Only: LINK
(how to share your site Read-Only link)

1 Like

Hello, @bennraistrick! Thanks so much for reporting this issue. Which project are you specifically having issues with? Can you share your read-only link with me so I can jump in and investigate?

Also, please feel free to contact the CST directly so we can help you solve this issue!

Hi this isn’t an issue with designer or project specific, its foundational to webflow as a whole, and how SSL and domains are handled. please do read what I have put. no matter the website this will occur,

try creating a base e-commerce site, hook up stripe and try publish to root and www you can’t you will get an error because you need CNAME flattening. however using 3rd party for this will have issue when the SSL renews.

1 Like

Hi, @bennraistrick! Thanks so much for the additional details! Having a specific site to investigate would really help us find the issue you’re mentioning.

Just as an aside, I do have an ecommerce store using the root and I am not having the same problems. So, it would be beneficial to see a site that is having that problem. Would love to take a look at a specific example and see if we can track this down!

However, if you don’t have one that’s ok! :webflow_heart: I can create another from scratch and do additional testing to see if it’s possible to recreate.

Hmm are you using both root and www. because stripe and apple pay would but publish for me.

https://preview.webflow.com/preview/husaco?utm_source=husaco&preview=e39274ceca2a0c967838183f1c7efbeb&mode=preview

1 Like

Thanks for sharing! Taking a look at your project now! :webflow_heart:

More context (www is set to default)

1 Like

Thanks, @bennraistrick - would you also be able to DM me a screenshot of your Cloudflare setup?

Sorry I had to remove cloudflair to fix the site but I use cloud flairs ns server and set the dns as you would for any domain tried both proxy and ssl-proxy the set flattening on the cname

1 Like

If you made a change, please don’t go through the trouble just to experiment. I have a test site and domain I can use! I’m working on it now and I’ll share more details very soon!

Hi, @bennraistrick!

Here’s a video I made showing you my setup and how it’s working using the root domain and Cloudflare:

CloudApp

I have a couple of clients who have been using the same setup for some time without issue as well. Let me know if this helps solve your issue!

Hi thank you for this however as per my message above 123reg hosting doesn’t support this method which is why there is a suggestion for the a records

1 Like

Hello!

Thanks so much for following back up! Yes, in order to use the root domain you would need to point the name servers to a DNS provider that supports CNAME flattening, like Cloudflare.

You can find a list of companies that support CNAME flattening here:

Let me know if you have any other questions and I’ll be happy to assist you further!

Ha and thus we arrive at the issue in my very first comment, my client cannot just switch domain provider and there will be many organisations which will be in the same situation.

Hi @bennraistrick

Thanks for sharing your feedback.

my client cannot just switch domain provider

Our team is aware of this limitation and this is something we hope to solve for in the future. I can’t provide a time frame quite yet but we hope to build out a more elegant solution for cases like this.

Thanks for your feedback and patience :bowing_man:

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.