I don't use cloudron and I only commented as when I was looking for the specific cloudflare error:
The service may be down or it may not be responding to traffic from cloudflared: x509: certificate is not valid for any names, but wanted to match localhost" cfRay=6957204cbdeb1fb9-SJC ingressRule=0 originService=https://localhost
I landed here from Google and I know that in the future, I will probably have this issue again and forget the solution.
So I'm posting this more for future me.
However, this would solve that specific issue that @girish was having,
I got my services up and going that used a self signed ssl cert and was able to proxy it with cloudflare.
It would be cool to try cloudron as it sounds like a really great product, but I personally don't have the budget for it at the moment.
@alexsunny123 ok there are quite a few variables in the mix here it seems. For a start, can you connect to the Cloudron setup view using the public IP address from your ISP on port 80 and 443?
To rule out some other maybe interfering parts, disable the Cloudflare proxying.
Since you mentioned email, on a residential connection you will most likely require a mail relay to work properly, anyways port 25 will most likely be blocked by your ISP. Cloudron as mail relay support for various providers though.
Lastly for Cloudron it doesn't really matter if bare-metal or VM, so there are no special docs about this. You should be fine as long as you have vanilla Ubuntu 20.04 server installed.
@robi yeah, with ecommerce being our primary business, we're invested in this. We have 12 very experienced devs on the team but just a few of them have had time to start looking at Cloudron this week. In this for the long-term though so I'm sure you'll start to see our work filtering through very soon.
@bangden07 Ah, that's a smart work around! I just noticed that you had SSL issues on the root domain. The wildcard cert only covers subdomains i.e *.foo.com but not foo.com. Cloudron still has to get normal certs for foo.com. I guess after a week, you can remove the cloudflare proxy.
THANK YOU. I use Cloudflare as my DNS provider. Looks like they have some sort of caching feature called Cloudflare Rocketloader which caused this conflict. I Turned it off and it worked now. Much appreciated! @nebulon