> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/fabricate/self-hosting-fabricate/configuring-fabricate/ca-certs-tls-https.md).

# Trusted CA certificates for TLS/HTTPS traffic

Your infrastructure might be configured to intercept outbound and HTTPS traffic. Instead of passing the original certificate through, it re-signs it with its own certificate. To do this, you might use a device such as a corporate L7/TLS-inspecting firewall, an egress proxy, or a network security appliance.

If this is the case, then you must configure the following environment variable

`FABRICATE_CA_CERT_FILE=<path to certificate file>`

For example:

`FABRICATE_CA_CERT_FILE=/custom-ca.crt`&#x20;

If you do not set this, then outbound HTTPS calls from Fabricate fail certificate verification, because the Fabricate container's default OS trust store does not contain the device certificate.

To enable Fabricate to use the certificate:

1. Get the CA certificate that the intercepting device presents.\
   \
   This might be a .crt or .pem file that the network team already has, or you might be able to export it from the device.
2. Mount the certificate file into the Fabricate container at any path.\
   \
   For example, you might use a Docker volume in **docker-compose.yml**:

{% code overflow="wrap" %}

```
volumes:
    - ./my-corporate-ca.crt:/custom-ca.crt
```

{% endcode %}

3. Set `FABRICATE_CA_CERT_FILE` to point to that path:\
   \
   `FABRICATE_CA_CERT_FILE=/custom-ca.crt`
4. Restart the container.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tonic.ai/fabricate/self-hosting-fabricate/configuring-fabricate/ca-certs-tls-https.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.