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

502 Bad Gateway when setting up Confluence Data Center on AWS

Dennis Andersen Oct 23, 2017

We’ve followed the guide for setting up Confluence Data Center on AWS using this quickstart/guide
Basically using all default values, the stacks are created successfully. But when we’re trying to access the stack output url to do the confluence setup wizard we just get a 502 Bad Gateway. Anyone else had issues with this or any clues? 

2 answers

1 accepted

0 votes
Answer accepted
Dennis Andersen Oct 31, 2017

So the issue was based in the EC2 instances not being initiated properly. More specifically Rebooting the Confluence Node(s) seemed to solve the issue. What this inital issue depended on I don't know, but if you have similar issues try restarting/terminating+creating a new node. 

Ann Worley Atlassian Team Oct 31, 2017

Thanks for following up to help others who run into this issue.

Dennis Andersen Nov 03, 2017

So I'm back at the 502 bad gateway now, and restarting the instances doesn't seem to work anymore. So this solution might not work.. 

0 votes
Ann Worley Atlassian Team Oct 24, 2017

To get the dialogue started, please let me know whether you used 

  1. Deploy Confluence Data Center into a new VPC on AWS

  2. or Deploy Confluence Data Center into an existing VPC

Screen Shot 2017-10-24 at 3.24.05 PM.png

Please make sure you're in a supported region per: Supported AWS regions

This guide may help as well: Running Confluence Data Center in AWS

If the Atlassian stack is generating, but we just can't hit it with the browser, it could be something with the load balancer configuration. In addition to working with us here at Atlassian, it may be useful to contact AWS.

Dennis Andersen Oct 26, 2017

Hi Ann, 

Thank you for the reply. We deployed into a new VPC and are in the region EU (Frankfurt). We also made sure to follow the guide you linked. AWS lists three running instances, and the CloudFormation Stacks were all successful, so it seems we're just missing something obvious. 

Dennis Andersen Oct 27, 2017

I also asked the question on the developer community over here:

Ann Worley Atlassian Team Oct 30, 2017

From the developer forum thread you linked, it looks like on Friday you resolved the issue by restarting the EC2 instances.

If you are all set now, please let us know any details that might help the next person who is setting up Confluence Data Center on AWS.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Confluence

Confluence CVEs and common questions

Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...

888 views 0 19
Read article

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