Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

502 Bad Gateway when setting up Confluence Data Center on AWS

Dennis Andersen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 23, 2017

Hi, 
We’ve followed the guide for setting up Confluence Data Center on AWS using this quickstart/guide https://aws.amazon.com/quickstart/architecture/confluence/
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? 
Cheers! 
Dennis

2 answers

1 accepted

0 votes
Answer accepted
Dennis Andersen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 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. 

AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 31, 2017

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

Dennis Andersen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 3, 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
AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 27, 2017

I also asked the question on the developer community over here: https://community.developer.atlassian.com/t/setting-up-confluence-data-center-on-aws/10294

AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 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
TAGS
AUG Leaders

Atlassian Community Events