Proxy and HTTPS setup for Confluence
Many customers choose to run Confluence behind a reverse proxy, often with HTTPS enabled. Getting your proxy configuration right is essential, to avoid problems later when using Confluence.
Proxy and HTTPS access are both configured in Tomcat, Confluence's application server.
If you plan to use collaborative editing, there are a number of proxy and SSL considerations you'll need to take into account when deciding the best way to configure your proxy.
In addition to the sample connectors, we also provide a number of step-by-step guides to help you enable HTTPS and configure your proxy correctly.
- Running Confluence Over SSL or HTTPS (terminating HTTPS at Tomcat)
- Running Confluence behind NGINX with SSL (terminating HTTPS at your proxy)
- Securing your Atlassian applications with Apache using SSL (terminating HTTPS at your proxy)
- Using Apache with mod_proxy (Confluence)
- Running Confluence behind NGINX with SSL (Confluence)
- Proxying Atlassian server applications with Apache HTTP Server (mod_proxy_http) (any Atlassian product)
- Proxying Atlassian server applications with Microsoft Internet Information Services (IIS) (any Atlassian product)
- Configuring Web Proxy Support for Confluence (Confluence)
- How to Configure Outbound HTTP and HTTPS Proxy for your Atlassian application (any Atlassian product)
Although we provide guides for some third-party solutions, and mention Apache and Nginx in the
server.xml file, you can choose your own proxy solution.
Atlassian Support can't provide assistance with configuring third-party tools like NGINX, Apache, or IIS. If you have questions, check your proxy server's documentation, ask the Atlassian Community, or get help from a Solution Partner.