SPS does not start and sends an HTTP error 503

Document ID : KB000050817
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

When starting the httpd.exe file and try to access the home page of the server, it gives a HTTP 503 error.
No logs are created for the proxy-engine and no errors are logged in httpd logs (error logs are in DEBUG level).

Solution:

HTTP error 503 means that the service is unavailable. According to RFC 2616, "the server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response."

When checking the installation log, it appears that the service could not be started after the installation had completed, failing on the error message:
"only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80"

Another Web Server or service is currently listening on port 80. You should reconfigure the SPS to use another port, or stop the another server if not in use.