[Sir_Cmpwn]

I challenge you to find a host you can't install this on: https://github.com/kristapsdz/acme-client-portable

If you bring up that you don't control the host (shared hosting), then we should shame the shared hosting provider, who has no excuse.

[supermdguy]

Heroku free dynos: https://devcenter.heroku.com/articles/ssl

[Sir_Cmpwn]

https://devcenter.heroku.com/articles/automated-certificate-...

[supermdguy]

"Heroku automatically manages TLS certificates for apps with Hobby and Professional dynos". It doesn't support free dynos.

[CiPHPerCoder]

You get to choose your own adventure here.

> Ask Heroku to support LetsEncrypt on all dynos.

> Vote with your wallets and move away from Heroku.

> Launch a competitor that allows others to move away from Heroku.

> _

[Sir_Cmpwn]

Then as I said: shame on Heroku.

[strictnein]

So the solution is to run code that I have no idea if it will function properly on my host to see if it will work? But this is all supposed to be super easy, right? I was just supposed to be able to run certbot, and now I just need to run this random package that I hadn't heard of until 5 minutes ago.

It's almost like this isn't a super simple process for everyone.

> "Conditional support for OpenBSD's sandbox, Mac OS X, or experimentally on Linux."

What now? I get to experience experimental functionality?