Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: Trying to run Let's ecnrypt SSL on Apache 2.4 Windows |
Page Previous 1, 2 |
Author |
|
DnvrSysEngr
Joined: 15 Apr 2012 Posts: 215 Location: Denver, CO USA
|
Posted: Fri 09 Apr '21 18:49 Post subject: |
|
|
Answers to your Questions:
1. How to find exact reason (e.g. check logs)? What logs? What to search through? - Look in your Error logs for Apache, should provide clues as to what failed and why.
2. How to force renewal if I don't want to change Apache configs? - What I have done in the past when I had a similar situation was this - I removed the folder I had for my Let's Encrypt / Mod_MD managed domains where my CERTS were kept named "ManagedDomains" in Apache (you might have a different folder name) and then restarted Apache. This allowed CERTS for all my domains to be recreated and created new entries in the Error log for each one. I then checked my Error log (don't let the name ERROR Log fool you - it contains lots of information that is not all ERRORS) to make sure all domains had their certs renewed.
Note: It you have a lot in your Error log, you may want to clear it or back it up and then clear it prior to restarting Apache to make searching for issues a bit easier.
This may or may not be the most ideal solution, but it is what worked for me. Once gain, "your mileage may vary."
--S |
|
Back to top |
|
EIKA
Joined: 22 Jan 2019 Posts: 43 Location: US
|
Posted: Fri 09 Apr '21 19:41 Post subject: |
|
|
Thank you very much for your reply. I cleared certs folders and got new certs after fixing mistake in config and Apache restart.
The problem was in my hosted - they added AAAA (IPv6) for my host and didn't informed clients. IPv6 pointed to their default Apache instead of mine. |
|
Back to top |
|
|
|
|
|
|