-
Notifications
You must be signed in to change notification settings - Fork 120
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
EB docker environment Nginx 502 gateway errors #140
Comments
Are you getting the 502 error on your Web Server or on your Worker Server? |
@joeyparis Thanks for the message. I resolved the 502 issue but still facing another issue. Environment EB
SQS
Issues
Can someone teach me how to solve this issue? |
What ports do you have exposed on the worker environment? Was the worker functioning prior to installing the gem or are you using this gem to get a worker in the first place? I apologize as I'm not as familiar with the Docker portion of the gem but I'll help how I can! |
Hi Joey,
I am crying now |
Are you deploying the same rails application code to both the web-env and worker-env? They should both be the same with the exception of the ENV variables. I'm not super familiar with the docker setup but you probably need to expose port 80 on the container so that Elastic Beanstalk's sqsd is able to publish the requests to the application. My guess is this is why jobs aren't processing but also why you're not seeing any errors.
When testing it in development are you also using SQS (or the localstack equivalent?)
This makes sense as the job is reaching the SQS queue, so the problem is definitely in the worker. I would see if you can find any logs for the |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Anyone has experienced that 502 gateway errors with this gem? After installing this gem, it raise nginx 502 errors. Hard to find any relevant logs regarding this issue.
The text was updated successfully, but these errors were encountered: