How to set Reverse Proxy and SSL parameters while running Atlassian Docker Images
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When running Atlassian products (Jira, Confluence or Bamboo) in Docker, the Tomcat's conf/server.xml file is automatically generated during container startup based on several environment variables.
The default container image does not have any reverse proxy configuration. The reverse proxy values can be passed during the container startup.
Environment
All supported Atlassian Docker image versions.
Solution
To set the reverse proxy values and maintain them please add the following environment variables to the Jira/Confluence/Bamboo Server Docker Container.
When executing via Docker Compose with a YAML file, adding the environment variables as:
...
confluence:
...
...
environment:
- "ATL_PROXY_NAME=<reverse_proxy_url>"
- "ATL_PROXY_PORT=<reverse_proxy_port>"
- "ATL_TOMCAT_SCHEME=https"
- "ATL_TOMCAT_SECURE=true"
...When executing directly via 'docker run' command, adding the following variables:
docker run --name confluence .... -e ATL_PROXY_NAME='<reverse_proxy_url>' -e ATL_PROXY_PORT='<reverse_proxy_port>' -e ATL_TOMCAT_SCHEME='https' -e ATL_TOMCAT_SECURE='true' ....If you are not using SSL on your reverse proxy URL, use 'http' and 'false' with the parameters ATL_TOMCAT_SCHEME and ATL_TOMCAT_SECURE, or remove them - as they are already set to 'http' and 'false' by default in the docker image.