-
Bug
-
Resolution: Fixed
-
High
-
None
-
6.0.0-beta3
-
5
-
Severity 2 - Major
-
When using AMPS to run Confluence for Development Synchrony doesn't seem to listen to HTTPS connections. I can go to http://localhost:8095/synchrony/resources/js/vendor/sockjs.min.js just fine, but I need to access confluence via HTTPS in order for it to interoperate with my add-on. Configuring Confluence to listen on HTTPS is quite simple, I just uncomment the https connector (defaults to port 8443) in Tomcat's server.xml. How do I make Synchrony listen on HTTPS?
To clarify, I'm not using any kind of external proxy. All I do to access confluence via HTTPS is by enabling the connector in tomcat's config file and going to https://dmitry.office.lucidchart.com:8443/confluence
Looks like the synchrony.proxy.enabled flag is false by default when I create a confluence insance with atlas-debug. I flipped it on and restarted confluence. That didn't seem to have an effect:
- https://dmitry.office.lucidchart.com:8443/synchrony-proxy/resources/js/vendor/sockjs.min.js returns a 404 with empty body
- The client still tries to openhttps://dmitry.office.lucidchart.com:8095/synchrony/resources/js/vendor/sockjs.min.js
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
[CONFSERVER-43804] synchrony-proxy web app does not work when running Confluence using AMPS and HTTPS
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 212572 ] |
| Workflow | Original: JAC Bug Workflow v3 [ 2896567 ] | New: CONFSERVER Bug Workflow v4 [ 3005687 ] |
| Workflow | Original: JAC Bug Workflow v2 [ 2787912 ] | New: JAC Bug Workflow v3 [ 2896567 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JAC Bug Workflow [ 2735496 ] | New: JAC Bug Workflow v2 [ 2787912 ] |
| Symptom Severity | Original: Major [ 14431 ] | New: Severity 2 - Major [ 15831 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2380465 ] | New: JAC Bug Workflow [ 2735496 ] |
Hey dmitry35, have you tried using the -u flag (mentioned above)? Otherwise, can you verify that the synchrony-proxy webapp is being deployed, either in the console output when running Confluence or in your plugin directory target (should be in target/container/tomcat8x/cargo-confluence-home/webapps)?
Dmitry [Lucidchart]
added a comment - Hi Vivian,
I still can't get synchrony to work in my local development environment. Here's my output from atlas-version:
$ atlas-version ATLAS Version: 6.2.15 ATLAS Home: /usr/share/atlassian-plugin-sdk-6.2.15 ATLAS Scripts: /usr/share/atlassian-plugin-sdk-6.2.15/bin ATLAS Maven Home: /usr/share/atlassian-plugin-sdk-6.2.15/apache-maven-3.2.1 AMPS Version: 6.2.11 -------- Executing: /usr/share/atlassian-plugin-sdk-6.2.15/apache-maven-3.2.1/bin/mvn --version -gs /usr/share/atlassian-plugin-sdk-6.2.15/apache-maven-3.2.1/conf/settings.xml OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0 Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T10:37:52-07:00) Maven home: /usr/share/atlassian-plugin-sdk-6.2.15/apache-maven-3.2.1 Java version: 1.8.0_131, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.4.0-92-generic", arch: "amd64", family: "unix"
It shows AMPS Version 6.2.11, but I set the maven-confluence-plugin version in pom.xml to 6.3.3. Should that do the trick?
But anyway, when I try to edit a page, this request returns a 404:
https://confluence-localhost.office.lucidchart.com/confluence/synchrony-proxy/heartbeat?_=1503416732569
My startup JVM args:
-Xmx8192m -Xms2048m -Dconfluence.velocity.deprecation.strictmode=false -Dreza.port=8095 -Dsynchrony.port=8095 -Dsynchrony.proxy.enabled=true<
Do you know what might be the issue?
Dmitry [Lucidchart]
added a comment - Hi Vivian,
I still can't get synchrony to work in my local development environment. Here's my output from atlas-version :
$ atlas-version
ATLAS Version: 6.2.15
ATLAS Home: /usr/share/atlassian-plugin-sdk-6.2.15
ATLAS Scripts: /usr/share/atlassian-plugin-sdk-6.2.15/bin
ATLAS Maven Home: /usr/share/atlassian-plugin-sdk-6.2.15/apache-maven-3.2.1
AMPS Version: 6.2.11
--------
Executing: /usr/share/atlassian-plugin-sdk-6.2.15/apache-maven-3.2.1/bin/mvn --version -gs /usr/share/atlassian-plugin-sdk-6.2.15/apache-maven-3.2.1/conf/settings.xml
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T10:37:52-07:00)
Maven home: /usr/share/atlassian-plugin-sdk-6.2.15/apache-maven-3.2.1
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" , version: "4.4.0-92- generic " , arch: "amd64" , family: "unix"
It shows AMPS Version 6.2.11, but I set the maven-confluence-plugin version in pom.xml to 6.3.3. Should that do the trick?
But anyway, when I try to edit a page, this request returns a 404:
https: //confluence-localhost.office.lucidchart.com/confluence/synchrony-proxy/heartbeat?_=1503416732569
My startup JVM args:
-Xmx8192m -Xms2048m -Dconfluence.velocity.deprecation.strictmode= false -Dreza.port=8095 -Dsynchrony.port=8095 -Dsynchrony.proxy.enabled= true <
Do you know what might be the issue? AMPS versions 6.3.1 and up now support HTTPS via the synchrony proxy.
Thanks Vivian,
running
Seems to make synchrony start up correctly and the editor loads, but the editing/saving experience is still mostly broken because I'm using H2 db 1.4 in my development, which isn't supported, but that's a separate issue.