In some cases, you might run into an issue opening Control Cockpit where Control Cockpit is not showing up properly and the services are not starting properly.
The issue is due to IIS(Microsoft Information Internet Services) or Apache(Tomcat) and Control Cockpit sharing the same access port (443.)
It is not always IIS or Apache(Tomcat) that causes this issue but it is the most common one! If you have an application that is hosting a website on your machine at localhost port 443, you will run into an error.
There are two options that can be explored:
1. Change the other application’s server configuration to use a different port than 443.
2. Adapt the Control Cockpit configuration to use a different port. This can be done by reinstalling the Cockpit and use any free port - for example, 8443 or 9443.
After reinstalling and defining a new web application port, you should have access to the Control Cockpit.
For Server installation:
If you are encountering an issue when you are setting this up for a Server rack, please check with your System administrator on what is installed on the VM, if you have any proxy setup on the same server unit but on another VM. This will likely cause an issue. You will need to reconfigure the proxy on your VM, do contact your server administrator for advice.