Hacker News new | ask | show | jobs
by strictnein 2881 days ago
> "I think the wins here far outweigh the temporary inconvenience of having to install/use certbot."

Installing certbot isn't something you can do on 100% of hosts. Switching hosts is also a pain.
1 comments
Sir_Cmpwn 2881 days ago
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.

link
supermdguy 2881 days ago
Heroku free dynos: https://devcenter.heroku.com/articles/ssl
link
Sir_Cmpwn 2881 days ago
https://devcenter.heroku.com/articles/automated-certificate-...
link
supermdguy 2881 days ago
"Heroku automatically manages TLS certificates for apps with Hobby and Professional dynos". It doesn't support free dynos.
link
CiPHPerCoder 2881 days ago
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.

> _

link
Sir_Cmpwn 2881 days ago
Then as I said: shame on Heroku.
link
strictnein 2881 days ago
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?

link