-
Notifications
You must be signed in to change notification settings - Fork 80
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 on redeploy #109
Comments
@brianlukoff did you find a fix? |
No - we use Galaxy now in part for this reason. |
For future searchers: I was able to fix by removing the browser policy. I'll add an update if I figure out how to add the browser policy back without getting the 503 error |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have multiple instances running using the cluster package, with Route 53 as DNS and no balancers. I have multiple Route 53 entries, each with the same hostname, that each point to the IP address of a different instance. This setup works well once deployed. But when I do a redeploy using mupx deploy, a connected client disconnects from the server (as expected) but then refreshes to a 502 Bad Gateway error page. Has anyone else run into this -- any ideas on how to work around?
The text was updated successfully, but these errors were encountered: