Hi all
I have now seen this 2 times that the Anacron job 'cron.daily' on my server change back the domain names to some old settings - WHY?
It is with months in between and correlate with server upgrade/reboot actions.
I have been using the contrib for some time and some month ago i "upgraded" to the Dehydrated version - the the problems started as I at the same time changed the domain names in domains.txt
/etc/cron.daily/call-dehydrated:
# INFO: Using main config file /etc/dehydrated/config
Processing beast.dk with alternative names:
** deleted **
+ Checking domain name(s) of existing cert... unchanged.
+ Checking expire date of existing cert...
+ Valid till Jan 21 05:34:00 2017 GMT (Longer than 30 days). Skipping renew!
And then it switches back to the old domains - why?
/etc/cron.daily/call-dehydrated:
# INFO: Using main config file /etc/dehydrated/config
Processing beast.dk with alternative names:
** deleted **
+ Checking domain name(s) of existing cert... changed!
+ Domain name(s) are not matching!
+ Names in old certificate: beast.dk
** deleted **
+ Forcing renew.
+ Checking expire date of existing cert...
+ Valid till Jan 21 05:34:00 2017 GMT (Longer than 30 days). Ignoring because renew was forced!
+ Signing domains...
+ Generating private key...
+ Generating signing request...
+ Requesting challenge for beast.dk...
+ Requesting challenge for
** deleted **
+ Responding to challenge for beast.dk...
+ Challenge is valid!
+ Responding to challenge for
** deleted **
+ Requesting certificate...
+ Checking certificate...
+ Done!
+ Creating fullchain.pem...
Set up modSSL db keys
Signal events
All complete
+ Done!
Is the old settings stored in the db or another file somewhere?
I can see that the domain.txt file was changed at 29/11 6:16. In the log files it looks as if I did a server upgrade/reboot at this time - but why does it change the domain.txt file?
/Benny