Resolution: Not a bug
Affects Version/s: 6.0.1, 6.0.2, 6.0.3
Fix Version/s: None
Component/s: Editor - Collaborative editing
Symptom Severity:Severity 2 - Major
QA Demo Status:Not Done
QA Kickoff Status:Not Done
Bug Fix Policy:
When Confluence is running behind a reverse proxy and the proxy settings are added to the server.xml file, the internal synchrony-proxy is automatically disabled. Following the Reverse Proxy with Internal Synchronyproxy documentation steps does not prevent the internal proxy from being disabled:
To turn on the Synchrony proxy:
- Edit <home-directory>/confluence.cfg.xml
- Set synchrony.proxy.enabled to true and save the file.
- Restart Confluence for the changes to take effect.
- Confluence running behind a reverse proxy (Apache, NGINX or IIS)
- Requests proxied to the internal synchrony-proxy instead of directly to synchrony
- Configure the proxy settings to point to the synchrony-proxy as in the documentation
- Make sure that the synchrony.proxy.enabled property is set to true in confluence.cfg.xml
Internal synchrony-proxy is enabled.
Internal synchrony-proxy is disabled automatically by the following step of the startup procedure:
This is a major issue when terminating SSL at Tomcat and running Confluence behind a reverse proxy, as synchrony does not accept direct HTTPS connections.
Add the following system property and restart Confluence: