Please note that this bug will disable the synchrony-proxy mode in 6.0.1.
If /synchrony is being used, you won't need to be worried about this bug.
After changing Confluence to use HTTPS configuration isSynchronyProxyRunning check fails with exception
Try importing the certificate into Confluence keystore https://confluence.atlassian.com/kb/unable-to-connect-to-ssl-services-due-to-pkix-path-building-failed-779355358.html
To convert an existing certificate key pair (e.g. configured in the Nginx configuration) to a Java keystore, please use the following commands:
OpenSSL for converting crt/key files to P12
Keytool for converting p12 to JKS
After that, we need to put the following line into the setenv.sh file:
or in the setenv.bat file:
Please note that the Confluence cannot detect if the proxy is running at startup. The user still needs to restart Synchrony (in the admin screen) to enable this internal proxy. (This issue will be fixed in 6.0.2)
In 6.0.2, http and localhost will be used as the scheme and hostname when checking the running status of the proxy. Since Tomcat cannot guarantee that it will finish starting up the synchrony-proxy before the healthcheck is executed (Therefore, this is a race condition). The synchrony-proxy will be assumed to be running always. If it is stopped for some reasons, the error will be logged out in the Confluence's log file.