Several Hubs Cloud users have reported issues of 502 gateway errors occurring on their Hubs Cloud deployments. This has been reported happening both soon after deployment, and in cases where the Hubs cloud stack has not been directly modified. Restarting the stack via a stack update seems to be one way that users have found to get around the issue.
It is unclear what happens that causes the gateway error, and whether or not there is a recommended best practice to work around the issue. Perhaps terminating the EC2 instance would be another potential thing to try, to see if the issue persists between server restarts without an update via the template.
Several Hubs Cloud users have reported issues of 502 gateway errors occurring on their Hubs Cloud deployments. This has been reported happening both soon after deployment, and in cases where the Hubs cloud stack has not been directly modified. Restarting the stack via a stack update seems to be one way that users have found to get around the issue.
It is unclear what happens that causes the gateway error, and whether or not there is a recommended best practice to work around the issue. Perhaps terminating the EC2 instance would be another potential thing to try, to see if the issue persists between server restarts without an update via the template.
┆Issue is synchronized with this Jira Task