It’s finally here!
5 Likes
It’s a revolutionary service, for NethServer as well
6 Likes
We’ll have it on our Discourse really soon
https://meta.discourse.org/t/support-for-lets-encrypt/22308/17?u=alefattorini
1 Like
some links to check…
FC24: https://bugzilla.redhat.com/show_bug.cgi?id=1287193
FC23: https://bugzilla.redhat.com/show_bug.cgi?id=1288742
EL6: https://bugzilla.redhat.com/show_bug.cgi?id=1288744
https://bugzilla.redhat.com/buglist.cgi?quicksearch=letsencrypt%20epel6
well, havin it on “our” discourse (an hosted app) isn’t really helpful 
and, BTW, having it running on a production server during the beta stage (certs expire after 3 months) is nor safe or smart…
the aim is to have it running on our servers, without the need of using git, and reducing almost to 0 the impact on the original install
centos6 comes with python 2.6 that is quite unsupported… upgrading python is not an option (will break yum), running letsencrypt with python2.7 using SCL is not easy as 1,2,3
People asked me many times https connection here and that’s the way. So, yes, it’s useful for me 
Guess we will have it definitely on 7
its 11 months already and I don’t know how to use it 
. Always set up my internal server with a self-signed cert. I read somewhere that you’ll need to renew every 3 months and the cert is only for a single server…wildcard not supported.
Certs are automatically renewed 
You can’t have a wildcard certificate, but you can have has many hostname you want inside the same cert!
1 Like