502 Bad Gateway on redeploy

[brianlukoff]

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?

[kylepierce]

@brianlukoff did you find a fix?

[brianlukoff]

No - we use Galaxy now in part for this reason.

[kylepierce]

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