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: mod_ssl.so not loading after upgrading from vs16 to vs17 |
|
Author |
|
FRubin
Joined: 08 Jun 2023 Posts: 2 Location: US, Aurora
|
Posted: Fri 09 Jun '23 15:22 Post subject: mod_ssl.so not loading after upgrading from vs16 to vs17 |
|
|
We are working on updating all of our Apache installs from VS16 to VS17. On my test machine, I added the new Apache and copied from VS16 the httpd.conf, the cert and key files, and some other configuration files from VS16. I then repeat the same steps I do during every upgrade, and test the conf files to ensure I did not miss anything as some installs have miscellaneous modules that need to be copied over. When I did httpd -t, I got the following error:
conf/httpd.conf: Cannot load modules/mod_ssl.so into server: The specified module could not be found.
I checked the modules directory to verify that it was present and it was there. I then noticed that we did not have the correct version Visual C++ Redistributable Visual Studio 2015-2022, so I updated that and rebooted the server. Following the reboot, I tested the conf again and received the same error.
This is on Windows Server 2016 Standard, and we are going from 2.4.56 VS16 to 2.4.57 VS17.
As a result of this step up to VS17, should I use the new httpd.conf file from VS17 and then copy over the custom configurations from the old file? Or is there something simple that I am missing?
Thank you all for your help, it is greatly appreciated! |
|
Back to top |
|
FRubin
Joined: 08 Jun 2023 Posts: 2 Location: US, Aurora
|
Posted: Fri 09 Jun '23 15:58 Post subject: re: mod_ssl.so not loading after upgrading from vs16 to vs17 |
|
|
This can be disregarded. Our ServerRoot in httpd.conf points to a symlink that we use so we do not have to modify the conf file each time. That symlink was pointing to the VS16 install and once I changed the ServerRoot to point to this version of apache, it found it. |
|
Back to top |
|
|
|
|
|
|