Let's Encrypt strange renew problem

Dennis

Dennis

Verified User
Joined
Nov 13, 2004
Messages
106
Location
The Netherlands
Hello,

The renewing process works for all certificates on multiple servers but one client get's strange errors.

The website sometimes loads with the right certificate and when I press F5 it loads with the expired certificate of two months ago.....

Can someone tell me what is wrong? I cannot find the old certificate on the server so where is it comming from?

Has this something to do with the multiple server settings?

Thanks in advance.
 
Hi Alex,

Thanks for the quick reply.

I have restarted the apache many times but not killed all the processes.....I think that did it.

Strange that some processes still remain when you restart httpd.

Thank you!
 
Wow, I have spent a few hours on this problem and finally I got this solution when I have registered to this forum. I can't believe it was that simple. Thank you!
 
zEitEr said:
Hello,

Code: 
killall -9 httpd
service httpd start
Click to expand...

I just spent hours trying to figure out why my old self-signed cert was showing up AS WELL AS the new cert I generated for my hostname. I even grep'd entire directories to look for a string from the cert that kept showing up and did quite a few apache restarts + generated new certs. The only thing that worked was your solution Alex. Thank you!

This should probably be in the knowledge base as it was a huge waste of time trying to figure out what was wrong :(
 
Unfortunately, I can't remember what the exact keywords were but I was looking for how to remove an SSL certificate that was assigned to a server.

What I was experiencing was that my new LetsEncrypt SSL certificate that I had just assigned to the server would sometimes be served up when loading up my server's hostname but it would also alternate between that one and a self-signed certificate I had made a year ago. I had deleted the cert from the server so it was very confusing as to why it was still showing up in my browser. I had cleared the cache and used a different browser but that solved nothing.

I had tried restarting apache/httpd but that apparently did nothing either. I was tempted to reboot the whole server, which probably would have fixed it as well, but that's a much worse idea than killing apache and starting it up again. I guess Apache had cached the certs?
 
Most services (including Apache) load their configs and other related files once at start (if they aren't going to write into them). So you can remove everything even binaries... until the process is stopped or killed it will serve most times well. It makes services to work faster. Of course Apache do not load all files from public_html or private_html.
 
You must log in or register to reply here.
Back
Top