By default, Dynatrace manages SSL for you — each Managed Cluster receives a dedicated subdomain of dynatrace-managed.com with a trusted SSL certificate. To use your own certificate instead, follow the steps below.
As of April 17, 2025, Chinese regulations require an ICP (Internet Content Provider) certification for all publicly accessible services using the dynatrace-managed.com domain. Since Dynatrace does not hold an ICP certificate due to the lack of a legal entity in China, our domains have been blocked by the local network providers.
To maintain monitoring capabilities, we recommend the following:
You need the SSL certificate and key files you received from your certificate authority (CA):
.cer or .cert).cer or .cert).pem)Encrypted private keys are not supported. To decrypt an SSL private key, run:
openssl rsa -in encrypted.ssl.key -out decrypted.ssl.key
encrypted.ssl.key — your encrypted SSL private key file.decrypted.ssl.key — the output file for the decrypted key.The command prompts you for the password and saves the decrypted key.
To disable automatic certificate management:
Without automatic certificate management, Dynatrace falls back to a self-signed certificate. Self-signed certificates are not trusted by browsers by default — on first access you'll see a security warning. Accept the exception in your browser's security settings to proceed, then install your trusted certificate as described in the next step.
Log in to the Cluster Management Console.
On the Home page, select the Cluster node that needs the new certificate.
On the Node Details page, select Edit SSL certificate.

Paste or upload the key files you received from your CA.
All keys and certificates must be in PEM format with full BEGIN and END headers.
Key format:
-----BEGIN PRIVATE KEY-----(Private Key)-----END PRIVATE KEY-----
Certificate format:
-----BEGIN CERTIFICATE-----(SSL Certificate)-----END CERTIFICATE-----
Select Save to upload the certificates.
Your certificate is tied to a specific hostname. To avoid a name-mismatch error, make sure the common name (domain name) in the certificate matches the address shown in the browser's address bar.