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
- How to identify Bamboo Release from buildNumber?
- Running a Bamboo build when releasing a version
- Running a Bamboo build when releasing a version
- Bamboo upgrade fails with error "Bamboo can be upgraded to version() only for DC Version License"
- Changing how Bamboo upgrades the Subversion working copy version during checkout
- Crowd 0.3 Beta Release Notes
- Crowd 0.3.2 Beta Release Notes
- Crowd 1.0.3 Release Notes
- Crowd 0.4 Beta Release Notes
- Bamboo deployment status
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 Feb 4, 2025
Related content
- How to identify Bamboo Release from buildNumber?
- Running a Bamboo build when releasing a version
- Running a Bamboo build when releasing a version
- Bamboo upgrade fails with error "Bamboo can be upgraded to version() only for DC Version License"
- Changing how Bamboo upgrades the Subversion working copy version during checkout
- Crowd 0.3 Beta Release Notes
- Crowd 0.3.2 Beta Release Notes
- Crowd 1.0.3 Release Notes
- Crowd 0.4 Beta Release Notes
- Bamboo deployment status
Powered by Confluence and Scroll Viewport.