Let's Encrypt Wildcard issues

[ugacomp]

Hello!
First of all I would like to thank the developers of Cloudron for doing a good job. I am using this platform to deploy a couple of websites for my client.

But I have also noticed a certain issue with Let's Encrypt Wildcard and Domain configurations: And let me explain:

When I deploy an app let's say WordPress with a domain like example.com, the final deployment with Let's Encrypt will be https://example.com. This works great! But again, when I try to access this very domain using www.example.com or https://www.example.com, I get an error and the site can't be accessed.

I think that this issue is kind of problematic because some people choose to use www.example.com, https://example.com. example.com and https://www.example.com

I request that the feature to allow all these kinds of setups for domains when the app is deployed should be considered.

If there is already a way to do it, please advise me and I will really appreciate

Thank you so much

[girish]

@ugacomp said in Let's Encrypt Wildcard issues:

When I deploy an app let's say WordPress with a domain like example.com, the final deployment with Let's Encrypt will be https://example.com. This works great! But again, when I try to access this very domain using www.example.com or https://www.example.com, I get an error and the site can't be accessed.

From DNS point of view example.com and www.example.com, are two different locations i.e you can have two completely different sites in those two places (though, of course, nobody does this in real life).

Anyway, the fix is just to add a "redirection" - https://docs.cloudron.io/apps/#redirections . Just put "www" redirection for your app and you are set.

[ugacomp]

@girish This worked like a charm. And everything is working as I wanted
And this script is going to change the web hosting industry. I think that it's one of the best scripts I've ever used in this industry. Thank you guys