Problem
If you have SSL enabled on an Apache server running on Mac OS X, you may have found that upgrading to 10.10.5 breaks your site, and your users cannot connect either via http or https.
It turns out the update moves the certs and keys to a new folder, so references to those certs are then broken.
Solution
To fix the issue, edit the /private/etc/apache2/extra/httpd-ssl.conf file:
sudo nano -B /private/etc/apache2/extra/httpd-ssl.conf
Then find the line that looks like SSLCertificateFile “/private/etc/apache2/server.crt” and change it to look more like SSLCertificateFile “/private/etc/apache2/ssl/server.crt”
Likewise, find the line that looks like SSLCertificateKeyFile “/private/etc/apache2/server.key” and change it to look more like SSLCertificateKeyFile “/private/etc/apache2/ssl/server.key”
Then, save the file and restart your Apache server:
sudo apachectl restart
Acknowledgements
Thanks to stamps-uk from Yosemite 10.10.5 Update Disabled Apache for the tip.
2 responses to “Fix for Mac OS X 10.10.5 breaking Apache”
[…] and upgrade from Yosemite to El Capitan, you'll get some breakage. The breakage won't be as bad as upgrading from 10.10.4 to 10.10.5 […]
[…] and upgrade from Yosemite to El Capitan, you'll get some breakage. The breakage won't be as bad as upgrading from 10.10.4 to 10.10.5 […]