-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
502 Bad Gateway after deploying #110
Comments
Did you find out how to solve this? I have the same issue. |
Guys do you have any fix for the missing node_modules? Is it a path issue? |
The same issue here, any solution? |
Hi, is this the first deploy? I suppose this is your first deploy with EBS perhaps in general or you are just migrating your environment to AL2 machines. You need to configure your ELB. Just make sure your machines are assigned to target groups, you have policies in place to only allow port 80 on EC2 machines and 443 on ELB (incoming from internet) and redirect 80 to 443 if you receive traffic on 80 from the internet. Your gateway issue, I believe, is due to traffic not reaching to your EC2 (where your Meteor is running). |
Hi all! I'm all pretty new to this but I hope someone could help here. I'm trying to host whats basically a "Hello world" equivalent of MongoDB, Meteor, React, Node.js app.
Meteor: 1.10.2
Node: v12.18.1
Here is my repository How to install if anyone wants to try it for themselves.
This works perfectly fine locally, and runs on http://localhost:3000/. When I try to deploy to AWS with the meteor-up mup-aws-beanstalk plugin, it deploys, but I get a 502 Bad Gateway error.
I'm pretty new to this but I did some research and checked the logs.
Checking the logs, I see that the start script isnt working properly
I checked the above problem and other StackOverflow questions mention to make the URL start with http or https, which my does.
Then there is also an error from nginx, there are these lines that keep repeating. I am not sure if these two are related.
This post describes the problem might be because the app isn't running on the server/port combination
HOWEVER, this post states that it might be because Elastic Beanstalk is reading the wrong file first, and therefore not opening up the ports in the first place?
I am not sure how or where to change the port numbers, or if this is a problem with npm.
This is my deployment output
and this is my mup.js file
The text was updated successfully, but these errors were encountered: