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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Where Can I configure Synchrony websocket to work since we upgraded

We upgraded our production server from 6.15.7 to 7.4.7, and now the editor does not work getting cannot save edit. Or cannot connect to server.


port 8091 inbound and outbound are open. 

I inherited this setup, and our test environment which should of been an almost exact mirror was not seeing this issue when we upgraded. 

When i put the Collab editing in limited mode, it allows people to edit and update pages again. 

failed: Error during WebSocket handshake: Unexpected response code: 200

I notice that we have had Apche2.4 installed, and could be being used as a proxy. 

But when searching for anything relating to 8091 as the port im not finding anything pointing to it being setup as such on either our test or production. 

My research and reading is point to websocket issues, but i do not know where to look for those. 

is there a default location? It mentions that since it is being managed by confluence services that I shouldnt need to edit the reverse proxt etc. 

1 answer

0 votes
Fabian Lim Community Leader Jan 05, 2022

Hi RJ,

You may want to review the following troubleshooting guide to find the root cause:

If it still persists, contact atlassian support.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events