Apache does not work after server 5.0.3 upgrade

I am having trouble getting basic services to work after the upgrade to Server 5.0.3 (what's new after a Server upgrade...).


This time it is Apache that does not want to work. The SSL server for the local server (the one that does the login for the users, the profilemanager etc) does not show up.


Reason seems to be that the proxy server that connects to the 'real' server has somehow lost its certifcates, as we can see in the settings in

/Library/Server/Web/Config/Proxy/apache_serviceproxy.conf.


Under


<VirtualHost *:443> and <VirtualHost *:8443>


I find:


SSLCertificateFile "PATH_PLACEHOLDER.cert.pem"

SSLCertificateKeyFile "PATH_PLACEHOLDER.key.pem"

SSLCertificateChainFile "PATH_PLACEHOLDER.chain.pem"


Does anyone know how to replace these things with sensible values?


Kind regards,

Johan Henselmans

Server-OTHER, OS X Server

Posted on Sep 17, 2015 2:11 AM

Reply
35 replies

Sep 24, 2015 2:03 PM in response to J Henselmans

For me, the solution ended up being simple. I had updated to server 5.0.4 and checked all the folders in regard to certificates etc and found everything in place. I administer two schools and in the mail server dns box i had school.school.nz I changed both servers to mail.school.school.nz and added all the E-Mail addresses and that cured the problem. I dont think this would have worked with 5.0.3 and Apple have "tweaked" something in 5.0.4. but adding mail to the domain name in the mail server does work 100% for me.

Sep 27, 2015 1:53 AM in response to J Henselmans

Another solution for a similar symptom.

Apache was loading, and the sites were listed as available, but the httpd server wasn't responding on port 80/tcp or 443/tcp


My SSL certs in /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf where all listed correctly, but the apache service proxy was starting and then immediately dying.


for my server, I traced the fault to another service/process running on 443/tcp (CrushFTP) that must have launched first, grabbed the 443/tcp and then when the apache service proxy tried to start, it couldn't grab the port so it quit. I checked the logs and it wasn't reporting the port as in use though.


I've now stopped the other process from using 443/tcp and the apache service proxy immediately stepped up and starting working.


Hope this helps someone else 🙂

Jan 8, 2016 12:31 PM in response to J Henselmans

The thing that ended up working for me was that I took all https calls out of my page, then I used .htaccess to rewrite my URLs. I had been rewriting http calls with PHP but that totally broke the page.


File Contents:

Options +FollowSymLinks


RewriteEngine On

RewriteBase /


RewriteCond %{HTTP:X-Forwarded-Proto} !https

RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]


Oddly I can't serve the page up on my local machine in Safari, even though I cleared all data from Safari -> Preferences -> Privacy. Works great in Firefox and Chrome. Also works great in Safari on everybody else's machine.


This took two days of searching and trying various things. I hope you have better luck than I resolving everything quickly. Arrgh!


Sidenote on upgrading to 5.04: If you have an existing directory named directory (mine was a staff directory) 5.04 will throw an error saying the website was turned off and can be turned on in the server application. It looks like you can't even create a directory named directory.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Apache does not work after server 5.0.3 upgrade

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.