GitHub user nickaccuweb added a comment to the discussion: HTTPS Does Not Work 
For Management Server

@fnavidan 

Based on the steps you've already tried, I would suggest checking a couple of 
things.

CloudStack 4.22 uses embedded Jetty for the management UI. Enabling HTTPS 
doesn't automatically disable HTTP or redirect HTTP traffic to HTTPS.

First, try accessing the UI directly using:

https://your-hostname:8443/client

If that doesn't work, check whether CloudStack is actually listening on port 
8443:

sudo ss -lntp | grep -E ':(8080|8443)\b'


Also, please verify the following settings in 
/etc/cloudstack/management/server.properties:

https.enable=true
https.port=8443
https.keystore=/etc/cloudstack/management/cloud.jks
https.keystore.password=YOUR_KEYSTORE_PASSWORD

One thing worth checking is the keystore itself. CloudStack may skip creating 
the HTTPS listener if the configured keystore file is missing. Make sure the 
file exists, is readable by the management service, and contains a valid 
PrivateKeyEntry with the certificate and private key.

You can verify it using:

sudo keytool -list -v -keystore /etc/cloudstack/management/cloud.jks

Also, check the management server startup logs to confirm whether 
`https.enable=true` is being picked up:

sudo grep "Initializing server daemon" 
/var/log/cloudstack/management/management-server.log | tail -5

If port 8443 is still not listening, could you share the output of the port 
check and the startup log entry? That should help narrow down whether the issue 
is with the HTTPS configuration or the keystore.

Alternatively, you can use Nginx or HAProxy for SSL termination and forward the 
traffic to CloudStack on port 8080. This is also a common approach for 
production setups.

CloudStack documentation for reference:
https://docs.cloudstack.apache.org/en/4.22.0.0/installguide/optional_installation.html#ssl-optional

Nick R
AccuWeb.Cloud

GitHub link: 
https://github.com/apache/cloudstack/discussions/13417#discussioncomment-19466038

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to