# Kan interne S3 niet gebruiken vanwege interne CA-certificeringsinstantie

**URL:** https://meta.discourse.org/t/unable-to-use-internal-s3-due-to-internal-ca-certificate-authority/169572
**Category:** Support
**Created:** [9 november 2020 om 04:03 UTC](https://meta.discourse.org/t/unable-to-use-internal-s3-due-to-internal-ca-certificate-authority/169572 "2020-11-09T04:03:00Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![teward](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/teward/32/148702_2.png) [@teward](https://meta.discourse.org/u/teward)
#### Post date: [9 november 2020 om 04:03 UTC](https://meta.discourse.org/t/unable-to-use-internal-s3-due-to-internal-ca-certificate-authority/169572/1 "2020-11-09T04:03:00Z")

</div>

We are using MinIO as an S3 endpoint for an internal Discourse, and it doesn’t seem to want to work with the internal resources because we use an internal CA authority.

Is there any way to get Discourse to use S3 and verify the SSL certificate by providing it the custom CA certificate to validate against?

Going into the app (Dockerized) with `launcher enter app` and then adding the certificate to the ca-certificates store _works_ to get `openssl s_client -connect discourse.s3.internal.domain` to connect AND validate the certificates (verify code: OK (0)) but apparently it doesn’t work for Discourse - gives this error on the Discourse page when trying to upload:

`SSL_connect returned=1 errno=0 state=error: certificate verify failed (unspecified certificate verification error)`

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [9 november 2020 om 14:46 UTC](https://meta.discourse.org/t/unable-to-use-internal-s3-due-to-internal-ca-certificate-authority/169572/2 "2020-11-09T14:46:37Z")

</div>

Did you restart the container after adding the certificate? (just a guess, that may not help)

---

<div class="post-metadata">

### Author: ![teward](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/teward/32/148702_2.png) [@teward](https://meta.discourse.org/u/teward)
#### Post date: [9 november 2020 om 15:03 UTC](https://meta.discourse.org/t/unable-to-use-internal-s3-due-to-internal-ca-certificate-authority/169572/3 "2020-11-09T15:03:24Z")

</div>

> Did you restart the container after adding the certificate? (just a guess, that may not help)

Yep, tried that but it did nothing.

Does Discourse keep a separate cert store independent of the container/system cert store?