diff --git a/src/docs/self-hosted/custom-ca-roots.mdx b/src/docs/self-hosted/custom-ca-roots.mdx index 630785d73b..dbedcf728c 100644 --- a/src/docs/self-hosted/custom-ca-roots.mdx +++ b/src/docs/self-hosted/custom-ca-roots.mdx @@ -2,7 +2,7 @@ title: "Self-Hosted Custom CA Roots" --- -Starting with Sentry `21.8.0`, if you need to have Sentry access services which do not have TLS certificates from publicly trusted CA roots, it's now possible to easily add them to the containers. Just add the certificates to the `certificates` folder inside the root of your Sentry install and restart the containers. Your custom CA roots will be used in addition to the publicly trusted CA roots. +Starting with Sentry `21.8.0`, if you need to have Sentry access services which do not have TLS certificates from publicly trusted CA roots, it's now possible to easily add them to the containers. Just add your `.crt` certificates in the PEM format to the `certificates` folder inside the root of your Sentry install and restart the containers. Your custom CA roots will be used in addition to the publicly trusted CA roots. While you can run update-ca-certificates in each container, that will update the system's root bundle on disk, but does nothing for any copies in memory. Restarting the container will update the bundle and make sure it is used.