# Self-Hosting an OpenSource LLM for DiscourseAI

**URL:** <https://meta.discourse.org/t/self-hosting-an-opensource-llm-for-discourseai/290923>\
**Category:** Self-Hosting\
**Tags:** ai\
**Created:** [January 8, 2024, 8:39pm UTC](https://meta.discourse.org/t/self-hosting-an-opensource-llm-for-discourseai/290923 "2024-01-08T20:39:55Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Eric\_Keller](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eric_keller/32/517693_2.png) [@Eric\_Keller](https://meta.discourse.org/u/Eric_Keller)\
**Post date:** [January 15, 2025, 4:16pm UTC](https://meta.discourse.org/t/self-hosting-an-opensource-llm-for-discourseai/290923/6 "2025-01-15T16:16:40Z")

</div>

Hey there, while exposing with a self-signed certificate vllm container on a GPU box on-prem, I did not find a good way to add the Root CA to the discourse container so it can access securely this on-prem service over https.

e.g.:

```plaintext
./launcher enter app
curl -L https://vllm.infra.example.com/v1/models
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

```

Is there a good way to add a self-signed root ca-certificate in the discourse container which would survive container image updates?

As far as I know adding it in the app.yml

```plaintext
run:
  - exec: wget ... && update-ca-certificates

```

would only work well while building/rebuilding the app.

Any hint welcomed.

---

_[View the full topic](https://meta.discourse.org/t/self-hosting-an-opensource-llm-for-discourseai/290923)._