> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/docker/8.x-9.x/workflowgen-image/tls-ssl.md).

# TLS/SSL

## Overview

This section presents ways to configure a secure connection (HTTPS) to the WorkflowGen container using a certificate. With Docker, containers run on an internal network, and only exposed ports will be available publicly. Therefore, you can't set up a TLS connection on one container only; you have to do it for all the containers, but this method doesn't scale well.

## Use an Nginx container

This method uses the Nginx web server as a reverse proxy configured with a TLS connection that will redirect all traffic to the WorkflowGen container(s). This method can be applied regardless of whether you have orchestration or not.

See the following pages for more information:

* [Let's Encrypt With Docker](https://devsidestory.com/lets-encrypt-with-docker/)
* [Secure services with TLS](https://docs.docker.com/ee/ucp/interlock/usage/tls/)

## Use Traefik

Traefik is a reverse proxy that handles routing, TLS termination, and load balancing, among other things. It's available as a container and you can use it in front of the WorkflowGen container. For more information about Traefik, see [its documentation page](https://docs.traefik.io/).

## Use Azure Application Gateway

In Azure, you can use the Application Gateway service in order to get a TLS connection for domains that you own. See the [Overview of TLS termination and end to end TLS with Application Gateway](https://docs.microsoft.com/en-us/azure/application-gateway/ssl-overview) Microsoft article to get you started.

## Kubernetes

For more information and recommendations about TLS/SSL handling in Kubernetes, see the [TLS/SSL](/docker/8.x-9.x/kubernetes/tls-ssl-kubernetes.md) page in the Kubernetes section.


---

# 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.workflowgen.com/docker/8.x-9.x/workflowgen-image/tls-ssl.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.