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
- Proxy and HTTPS setup for Confluence
- Confluence is Not Accessible with a 502 Proxy Error
- Using Apache with mod_proxy
- Possible Confluence and Synchrony Configurations
- Can't check base URL warning in Confluence 6.6 or later
- Confluence Collaborative Editing does not work with SSL and Apache 2.4.9 or earlier
- Troubleshooting Collaborative Editing
- Tomcat 9.0.33 shipped with Confluence 7.4 binds to localhost by default when using AJP connector
- How to use NGINX to proxy requests for Confluence
- Configuring Web Proxy Support for Confluence
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 Oct 3, 2024
Related content
- Proxy and HTTPS setup for Confluence
- Confluence is Not Accessible with a 502 Proxy Error
- Using Apache with mod_proxy
- Possible Confluence and Synchrony Configurations
- Can't check base URL warning in Confluence 6.6 or later
- Confluence Collaborative Editing does not work with SSL and Apache 2.4.9 or earlier
- Troubleshooting Collaborative Editing
- Tomcat 9.0.33 shipped with Confluence 7.4 binds to localhost by default when using AJP connector
- How to use NGINX to proxy requests for Confluence
- Configuring Web Proxy Support for Confluence
Powered by Confluence and Scroll Viewport.