hi !
First > thank you for these explanation, I understand a little better what I do... So,
- I updated smeserver-letsencrypt to v0.5-11.
- switched letsencrypt to test mode
following config :
[root@sme-lurey ~]# config show letsencrypt
letsencrypt=service
ACCEPT_TERMS=yes
API=2
configure=none
email=xxxxxx@xxxxxxx.fr
hookScript=disabled
status=test
[root@sme-lurey ~]# cat /etc/dehydrated/config
#!/bin/bash
CA="https://acme-staging-v02.api.letsencrypt.org/directory"
WELLKNOWN="/home/e-smith/files/ibays/Primary/html/.well-known/acme-challenge"
HOOK="/usr/bin/hook-script.sh"
BASEDIR="/etc/dehydrated"
CONTACT_EMAIL=xxxxxx@xxxxxxx.fr
API="2"
PARAM_ACCEPT_TERMS="yes"
- run
# dehydrated -c -x (with -x, otherwise nothing was done, since I already had a valid certificate.)
> Then :
- runs normaly, ends without errors.
- "fake-certificate" deployed, can be seen as told in the wiki
- I returned to enabled mode
following config :
[root@sme-lurey ~]# config show letsencrypt
letsencrypt=service
ACCEPT_TERMS=yes
API=2
configure=none
email=xxxxxx@xxxxxxx.fr
hookScript=disabled
status=enabled
[root@sme-lurey ~]# cat /etc/dehydrated/config
#!/bin/bash
CA="https://acme-v02.api.letsencrypt.org/directory"
WELLKNOWN="/home/e-smith/files/ibays/Primary/html/.well-known/acme-challenge"
HOOK="/usr/bin/hook-script.sh"
BASEDIR="/etc/dehydrated"
CONTACT_EMAIL=xxxxxx@xxxxxxx.fr
API="2"
PARAM_ACCEPT_TERMS="yes"
All right, new (real) certificate is deployed.