After stopping and starting the management server it is no longer accessible. Loading the default page (https://<server>:8443) and clicking the "Launch" button does not load the username/password login page as expected.
If clicking the launch button does return an error then it is likely different from the problem that this article describes and you can review TEC1046022 to see if that helps.
CA Release Automation version 5.5.2
1 Management Server
1 Execution Server
The problem described above was seen after an attempt to configure an execution server, already added to the management server communicating using 8080/http, to use non-standard ssl certificates. This involved updating the necessary configuration files on the execution server, recycling the execution server and changing the properties for the execution server in the Automation Studio -> Agent Management view to use 8443/https.
In this case, the server.xml was configured to use a keyAlias that could not be found in the keystore file referred to by server.xml keystoreFile configuration setting. The wrong keystore file name was used. So the keystore file name specified in the conf/server.xml and also in the webapps/execution/WEB-INF/jms.properties file.