mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-11 22:30:44 +01:00
When I change DNS name in new cert for the same client, dehydrated is doing new cert but not activating it #284
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bobykus on GitHub (Feb 20, 2018).
F.x. I had ssl cert for domain.com
-rw------- 1 root root 3243 Feb 16 11:26 privkey-1518776816.pem
-rw------- 1 root root 1687 Feb 16 11:26 cert-1518776816.csr
-rw------- 1 root root 2175 Feb 16 11:26 cert-1518776816.pem
-rw------- 1 root root 1684 Feb 16 11:26 chain-1518776816.pem
-rw------- 1 root root 3859 Feb 16 11:27 fullchain-1518776816.pem
lrwxrwxrwx 1 root root 22 Feb 16 11:27 privkey.pem -> privkey-1518776816.pem
lrwxrwxrwx 1 root root 20 Feb 16 11:27 chain.pem -> chain-1518776816.pem
lrwxrwxrwx 1 root root 24 Feb 16 11:27 fullchain.pem -> fullchain-1518776816.pem
lrwxrwxrwx 1 root root 19 Feb 16 11:27 cert.csr -> cert-1518776816.csr
lrwxrwxrwx 1 root root 19 Feb 16 11:27 cert.pem -> cert-1518776816.pem
then I requested cert for two DNS names domain.com and www.domain.com by running
/usr/local/sbin/dehydrated --accept-terms --cron --config $UserHome/ssl.conf/$ServerName/.letsencrypt/config
and received it successfully
Processing domain.com with alternative names: www.domain.com
but old links remains even new cert is issued!
lrwxrwxrwx 1 root root 22 Feb 16 11:27 privkey.pem -> privkey-1518776816.pem
lrwxrwxrwx 1 root root 20 Feb 16 11:27 chain.pem -> chain-1518776816.pem
lrwxrwxrwx 1 root root 24 Feb 16 11:27 fullchain.pem -> fullchain-1518776816.pem
lrwxrwxrwx 1 root root 19 Feb 16 11:27 cert.csr -> cert-1518776816.csr
lrwxrwxrwx 1 root root 19 Feb 16 11:27 cert.pem -> cert-1518776816.pem
-rw------- 1 root root 3247 Feb 20 08:18 privkey-1519111116.pem
-rw------- 1 root root 1716 Feb 20 08:18 cert-1519111116.csr
-rw------- 1 root root 2204 Feb 20 08:18 cert-1519111116.pem
-rw------- 1 root root 1684 Feb 20 08:18 chain-1519111116.pem
-rw------- 1 root root 3888 Feb 20 08:18 fullchain-1519111116.pem
It is lead to dehydrated keep trying to renew existed cert until reach the limit 5 certs a week.
What I am doing wrong? How can I activate new cert with dehydrated?
The config file looks
BASEDIR=/somepath/domain.com
CERTDIR="/somepath/ssl.conf"
WELLKNOWN="${BASEDIR}/.well-known/acme-challenge"
ACCOUNTDIR="/somepath/ssl.conf/domain.com/accounts/"
DOMAINS_TXT="${ACCOUNTDIR}/domains.txt"
RENEW_DAYS="14"
ACCOUNT_KEY_RENEW="no"
domains.txt looks like
domain.com www.domain.com