4 ms·

> sorry about the bad SSL cert I'm curious, why not just serve plain HTTP at that point? It makes little difference to the viewer.

• rsync 3y ago
  I think I may do that. Or buy a "real" SSL cert that I don't need to fiddle with every few months. I think there are some browsers that won't even connect to HTTP/80 without a warning ?
  • gottorf 3y ago
    I've used Namecheap/PositiveSSL[0] for stuff like that in the past; under $10/year, and never had any issues. [0]: https://www.namecheap.com/security/ssl-certificates/ https://www.namecheap.com/security/ssl-certificates/
    • rsync 3y ago
      Bottom line: so pleased that I had acme.sh sandboxed in a jail to generate certs… what a shitshow that ended up being…
    • __d 3y ago
      LetsEncrypt is free, and sure, you have to run the cron job to cycle the certs, but honestly, it's painless.
  • cvalka 3y ago
    Use Lego and Dagu
  • numpad0 3y ago
    if it's just(JUST) for the padlock icon, you can setup Cloudflare free plan with the proxying enabled