https://bugs.contribs.org/show_bug.cgi?id=10595
--- Comment #2 from John Crisp <[email protected]> ---
There ya go:
https://www.reetspetit.com/smeserver/6/repoview/smeserver-letsencrypt.html
I am not going to add it to CVS for now as I am going to renumber it to 0.5 or
0.6 (in line with dehydrated) so this is just for testing.
Vague Howto - dehydrated / letsencrypt update to v2 API
Needs updated smeserver-letsencrypt and depends on v0.6 of dehydrated
For now grab the rpm from my repo above
Set letsencrypt to test:
config setprop letsencrypt status test
signal-event console-save
Install rpm:
yum localinstall smeserver-letsencrypt
signal-event post-upgrade;signal-event reboot
Check your /etc/dehydrated/config file especially the CA line - should be
acme-staging-v1
Set to letsencrypt enabled and console save
CA should now be acme-v01.api
Now we can try v2. (The code defaults to v1 API so it doesn't wreck your
installation)
Set letencrypt to test again, and now set API 'v2'
config setprop letsencrypt API v2
signal-event console-save
Check config for CA acme-v02.api
Now set letsencrypt to enabled and console-save.
(Note if you set 'auto' then there will be no CA line as it accepts the default
v02 in the dehydrated script)
With auto your config file should look a bit like this with no CA line as the
default in dehydrated is now v2. If you set API v2 there should be a CA line.
#!/bin/bash
WELLKNOWN="/home/e-smith/files/ibays/Primary/html/.well-known/acme-challenge"
BASEDIR="/etc/dehydrated"
HOOK="/usr/bin/hook-script.sh"
API="auto"
PARAM_ACCEPT_TERMS="yes"
Now try to update:
dehydrated -c -x
dehydrated --cleanup
You should see some waffle about v2 API / URLs
That should be it..... YMMV :-)
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
