The SSL Problem and a simple Solution

[CoderGeeK]

When hosting applications on evernode instances you can't assume that it comes with a wildcard certificate, and even if it does, you probably can't access it from within the docker container. This is problematic as https is increasingly important.

There are probably a lot of solutions to this, but the one I have come up with is simple: Use your own ssl certificate and your own domain.

I pick an instance, and I ping it to get it's ip. I then point my domain to it and generate a ssl certificate on a provider where dns records are enough to verify my domain.

I found a provider that is offering free domains, and they seem to work well, link below
freedomain.one

With the help of that domain provider I'm able to point towards my future evernode instance, and to generate my SSL certificate I use zerossl.com for a free certificate.

And voilá,
Whichever application you deploy can now use your own domain and your own ssl certificate!


Better ideas and thoughts about the future are welcomed

[XRPLWin]

Guide how to connect trough Cloudflare would help.

[wroomwroom]

Guide how to connect trough Cloudflare would help.

But then we're relying on cloudflare, increasing the overall centralization of the internet! Not sure if that is what we want?

I agree though, politics aside, cloudflare is a very smooth solution to this problem!