List of Client Implementations - Add client

rugk · 2016-01-16T11:06:36.815Z

Continuing the discussion from List of Client Implementations:

As I cannot reply there any more (do not ask me why), please add the following client by @serverco:

Pros and cons of 90-day certificate lifetimes Issuance Policy

@…

GitHub - srvrco/getssl: obtain free SSL certificates from letsencrypt ACME server Suitable for automating the process on remote servers. - Bash

CC: @jcjones

eva2000 · 2016-01-16T16:59:47.546Z

thanks @rugk loving all the bash related client implementations… something i can follow

jcjones · 2016-01-19T14:12:04.166Z

Added it; I’m guessing the whole Documentation category may be locked from most posters? Anyway, sorry for the (holiday) delay.

jahid · 2016-01-20T02:21:52.555Z

@jcjones
This is a (~350 line) Python script based on acme-tiny (~200 line): letsacme
It simplifies getting certificate for shared servers/hosting while supporting the acme-tiny options too and includes some other additional features.

Can you add it too…

jcjones · 2016-01-20T02:28:42.940Z

jahid:

It simplifies getting certificate for shared servers/hosting while supporting the acme-tiny options too and includes some other additional features.

I'll add it, but just FYI, since you don't have issues enabled on your repo: Please be cautious advising folks to only renew at 00:00 on the 1st of each month. It's dangerous to prompt a big load spike at that time, especially if some random % of requests time out and don't retry before expiry. It's better to toss in some randomness in the time, and much better to have the opportunity for retries by trying daily. See Getting Started - Let's Encrypt

eva2000 · 2016-01-20T03:16:27.103Z

jcjones:

See Getting Started - Let's Encrypt

Oooh nice info there of other flags I wasn't really aware of i.e. --keep-until-renewal

and yes i insert a random sleep interval into my auto renewal cron for my letsencrypt integration so ends up something like

sleep XXXs ; /usr/bin/bash /usr/local/nginx/conf/ssl/le20.http2ssl.xyz/letsencrypt-le20.http2ssl.xyz-cron > /dev/null 2>&1

where XXX is randomised.

jahid · 2016-01-20T03:16:58.004Z

jcjones:

I'll add it, but just FYI, since you don't have issues enabled on your repo: Please be cautious advising folks to only renew at 00:00 on the 1st of each month. It's dangerous to prompt a big load spike at that time, especially if some random % of requests time out and don't retry before expiry. It's better to toss in some randomness in the time, and much better to have the opportunity for retries by trying daily. See Getting Started - Let's Encrypt

Sorry about the issue not being enabled. I have enabled it now. And yes I will look into it ( I just copied that cron job code from acme-tiny). Thanks for your assistance..
Regards,
Jahid

trim · 2016-08-22T11:40:06.493Z

Hello,

I’ve also forked the acme-tiny python client to create a new acme client : acme-dns-tiny (with Github mirror).

It’s goal is also to be tiny, easily readable and it uses DNS verifications to validate domains by use of standard dynamic DNS update messages (with TSIG key authorizations).

I hope it could be useful for let’s encrypt community

Regards,
Adrien

rugk · 2016-08-22T17:40:49.228Z

You can add it by yourself by editing the initial post in the main thread.

trim · 2016-08-22T18:44:30.329Z

I didn’t know, thanks

eva2000 · 2016-08-23T05:54:17.965Z

oh didn’t know we could edit ourselves