Certain types of containers don’t support the Let’s Encrypt addon. Docker and VPS containers are examples of that. In those cases the best way to do it is to add a Load Balancer to the environment and you can then add the Let’s Encrypt addon to the load balancer which will proxy those requests. Jim models that in this thread https://forums.reclaimhosting.com/t/adding-a-custom-domain-to-a-reclaim-cloud-environment/3133
My 2 cents if you do not mind, the mentioned approach using load balancer is the simplest way. But just to give you a full picture, there is also a possibility to integrate Jelastic Let’s Encrypt Add-on with custom (aka non-certified) containers via deployHook. A few examples how it works
@siruslan Oh cool, I’ll look into adding that as a possibility for the installers we build, would definitely make the process of using custom domains a bit more straightforward.
I’m currently moving my azuracast install over to Reclaim Cloud and I’ve had success keeping it behind the Shared Load Balancer (so the built in SSL works), but then using the Endpoints feature in Jelastic to open up the port that I need to connect to stream. I have it configured like this: