After enabling SSL on SPS Apache it starts but the port is not opened

book

Article ID: 77676

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) AXIOMATICS POLICY SERVER CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction



We have configured SSL on the SPS Apache manually by following the documentation steps, however when we restart the SPS and we try to access to https://SPSFQDN:443/ on the browser we get a Connection refused error.

When we run a netstat command at the OS prompt, we see the port TCP 443 is not opened. However, the SPS has started as we can access on port 80 as usual. We have verified the httpd.conf and extra/httpd-ssl.conf are correct, and we modified the spsapachessl.properties file as per the documentation, and we followed the same steps on a different SPS server which worked fine.

How can we solve this?

Environment

SPS R12.52 SP1 

Resolution

The problem was caused by an incorrect stop of the proxy engine before which left the sps.pid file in the /proxy-engine/tmp folder. When the SPS was stopped the file was not deleted correctly. After removing the sps.pid file the SPS is able to start opening both 80 and 443 TCP ports.

Additional Information

https://docops.ca.com/ca-single-sign-on/12-52-sp1/en/configuring/ca-siteminder-sps-configuration/configuring-ssl-for-ca-siteminder-sps/configuring-ssl-on-apache-web-server-manually/