Using Apache with mod_jk
Proxy and HTTPS setup for Confluence
- Configuring Web Proxy Support for Confluence
- Connecting to LDAP or Jira applications or Other Services via SSL
- Using Apache with mod_proxy
- Running Confluence behind NGINX with SSL
- Running Confluence Over SSL or HTTPS
- Using Apache to limit access to the Confluence administration interface
- Using Apache with mod_jk
- Using mod_rewrite to Modify Confluence URLs
On this page
Related content
- Clustering with Confluence Data Center
- Performance issue with Confluence due to Jira Metadata plugin
- CPU Usage Spikes to 100 percent on Virtual Server and Confluence Becomes Unavailable
- Set up a Synchrony cluster for Confluence Data Center
- Create a staging environment for upgrading Confluence
- Embedded H2 Database
- Supported Platforms
- Confluence Data Center disaster recovery
- Configuring Logging
- Preparing for Confluence 10.0
It's not possible to use only mod_jk to proxy Confluence 6.0 or later. This is because Synchrony, which is required for collaborative editing, cannot accept AJP connections. The preferred configuration is Using Apache with mod_proxy.
If you are unable to switch to mod_proxy, see [ARCHIVED] How to configure Apache mod_jk to proxy Confluence 6.x or later for a workaround.
Last modified on Nov 1, 2017
Related content
- Clustering with Confluence Data Center
- Performance issue with Confluence due to Jira Metadata plugin
- CPU Usage Spikes to 100 percent on Virtual Server and Confluence Becomes Unavailable
- Set up a Synchrony cluster for Confluence Data Center
- Create a staging environment for upgrading Confluence
- Embedded H2 Database
- Supported Platforms
- Confluence Data Center disaster recovery
- Configuring Logging
- Preparing for Confluence 10.0
Powered by Confluence and Scroll Viewport.