Topic: Letsencrypt domain names change back to old settings

[beast]

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

Code: [Select]

/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?

Code: [Select]


/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

[guest22]

contrib or manual letsencrypt?

[beast]

contrib or manual letsencrypt?

I have followed the guide at https://wiki.contribs.org/Letsencrypt from back when it was quite new and to the current version.

The last time I did the steps I did it manual - but to be honest I do not really remember what I have done in the past

I can see that one explanation is that I have used a contrib in the past and it is still there and overwrite the domain.txt file at upgrade with settings from the db!

How do I check if this is the case and fix it?

/Benny

[guest22]

See https://wiki.contribs.org/Letsencrypt#Install_with_John_Crisp_contrib

[beast]

See https://wiki.contribs.org/Letsencrypt#Install_with_John_Crisp_contrib

I checked the contribs I have installed with the command: /sbin/e-smith/audittools/newrpms

and smeserver-letsencrypt.noarch is installed

So I updated the db configuration with

db hosts setprop www.mydomain.com letsencryptSSLcert enabled
db domains setprop mydomain.com  letsencryptSSLcert enabled

and hope this will solve the situation

Thank you

[ReetP]

Sorry I have not been around much recently due to buggering my back

Let me know if you have any issues - I don't visit the forums very often and I am hoping we can get letsencrypt into contribs sometime soon so issues can be reported as bugs and I will then see any bug reports.

B. Rgds
John

[beast]

Sorry I have not been around much recently due to buggering my back

Let me know if you have any issues - I don't visit the forums very often and I am hoping we can get letsencrypt into contribs sometime soon so issues can be reported as bugs and I will then see any bug reports.

As far as I know it works fine for now