Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

need to change the port for accessing synchrony

This question is in reference to Atlassian Documentation: Administering Collaborative Editing

Hello all,

if we use the default config for synchrony, the internal proxy has problems to access the localhost because confluence is running in a docker and internal proxy should prefer confluence:8091/... for localhost:8091 to access the synchrony. If we proxy the requests to synchrony via nginx and disable the internal confluence proxy, such config works as expected with the one exception: confluence generates synchrony urls with port :8091 and this port should be opened extra on a host machine. The responses from :8091/synchrony and :80/synchrony are now the same and both work well, but the web pages want to go to :8091.

We would like either to say the confluence to access  synchrony via internal proxy under the specific hostname (eg. confluence:8091) or to say what port should be used to access the synchrony, if the internal proxy is disabled (in our case 80).

We use confluence 6.0.1 in Docker + Oracle JDK 8

Any hints would be appreciated!

Kind regard,

Gena

 

3 answers

1 accepted

0 votes
Answer accepted

Port is configurable by adding the following line (say your preferred port is 9004) to /bin/setenv.sh

CATALINA_OPTS="-Dsynchrony.port=9004 ${CATALINA_OPTS}"

Cheers,

Zlatko 

Synchrony's port can be specified with -Dreza.port (not -Dsynchrony.port - see https://jira.atlassian.com/browse/CONF-45565).

I'm not sure I follow re. confluence:8091. Synchrony binds to :8091 on all interfaces by default. Confluence (6.0.2 anyway) hardcodes 'localhost' in its 'Synchrony Internal Service URL' - see https://jira.atlassian.com/browse/CONF-45567

We are on 6.0.3 in a docker now. The synchrony proxy is enabled. Following nginx configuration works (important is the location /synchrony-proxy):

location /synchrony-proxy {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://confluence:8091/synchrony;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
    }
 
 
 
 location / {
                proxy_set_header Host $http_host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_redirect off;
                proxy_pass http://confluence-backend;
        }
 
}

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Asked in Jira Service Desk

Calling all Insight users, we need your help!

Hello Insight users,  As part of our (Mindville's) acquisition by Atlassian, our training team is looking to build some new Insight training materials. It would really helpful if you can ...

163 views 1 1
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you