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
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.
Thanks for following up to help others who run into this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To get the dialogue started, please let me know whether you used
Deploy Confluence Data Center into a new VPC on AWS
or Deploy Confluence Data Center into an existing VPC
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.