Topic: Apache 2.2 on Mac Server 5.2 , Sierra

[hkxl]

Hello,

I realise this is a all vintage stuff, but I need to have this server up and running for 6 more months. The mac server interface shows that Apache is up and running, but it is not serving any page. As the server other services are doing well I suspect it is related to Apache. Hence my question on this forum.

The issue started when I deleted one certificate. The error log (under /var/log/apache2/service_proxy_error.log) shows this line :

[... Syntax error on line 215 of /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf:
SSLCertificateFile: file '/etc/certificates/example.domain.com.76EA32A02BEFC81EFC4B31FA08C84A262AF93464.cert.pem' does not exist or is empty …])

(nb: example.domain.com replaces the real name)

When I look at the that file at line 215 it shows this : SSLCertificateFile "/etc/certificates/${CERT_ID}.cert.pem"

those values seem come from a file called servermgr_web_apache2_config under /Library/Server/Web/Config/apache2

That entry on that file apache_serviceproxy.conf is

<dict>
<key>SSLPassPhrase</key>
<dict>
<key>Port</key>
<string>443</string>
<key>SSLCertificateKeyFile</key>
<string>/etc/certificates/example.domain.com.76EA32A02BEFC81EFC4B31FA08C84A262AF93464.key.pem</string>
<key>ServerName</key>
<string></string>
<key>enabled</key>
<true/>
<key>mstCertificateIdentifier</key>
<string>SHA-256:3d7b608faa3c8936d5015652ae1c9b203eb40af444cc3444862201aa821d4a6d:"example.domain.com"</string>
<key>sslCertificateIdentifier</key>
<string>example.domain.com.76EA32A02BEFC81EFC4B31FA08C84A262AF93464</string>
</dict>
<key>_id_</key>
<string>*:443_</string>
</dict>




But as that certificate is no more I wonder why this entry is there and if that is not the reason why Apache does not delivers the pages.

This issue is beyond me. I need help to solve this issue on that server. Any help is welcome (replacing that server for now is not an option due to legacy issue on one project.)

Any idea? Thank you, hkxl

[James Blond]

My guess is that the apache_serviceproxy.conf has a configuration for reverse proxying to a backend server and apache does the SSL termination for that server.

Please post the apache_serviceproxy.conf file