502 Error, Randomly occurs on established service

I have an established service with a Rails web service and a Database service, using custom URL. I have a few puma workers. The application loads just fine…most of the time.

Every once in a while, any GET or POST could result in a 502 gateway error. I got one this morning when going to the root URL. When it happens is random, and there is zero information in the logs (I have the request ID of my last one).

1 Like

No reply. Any thoughts?


I made a request to your service and conveniently enough I got a 502 error as well, taking the rayID that’s exposed on the error page I was able to look up the request and can see that we responded with a 502 from the Render proxy, what would be useful would be to get the header x-render-routing value as this can further help debugging what the cause for this is. All my subsequent requests were successful though.

John B

Hi @John_B,

I have seen these errors pop in and out as well and managed to catch both the rayID and the x-render-routing header for my app. This seems to happen right as a new deploy is switching over from the old servers to the new servers.

Request / CF RayID: 76165a65b059636c-ORD
x-render-routing: dynamic-paid-error

I found this other thread referencing the “dynamic-paid-error”:

It suggests it is our application that served the error. Digging into our logs, I can see:

  1. Our new service instance was spun up and served its first healthcheck request at 2022-10-28T20:15:32.468842Z. (syslog.appname = web-svrgt)

  2. Render sent the shutdown signal to our old service instance running the Puma web process (were running rails) at 2022-10-28T20:16:37Z. (syslog.appname = web-6d667)

  3. The Date response header here indicates that this request happened at 2022-10-28T20:16:51Z (Fri, 28 Oct 2022 20:16:51 GMT).

  4. The only request logs around the time of the failed browser request on the new server instance were successful healthcheck requests.

Given this, it seems like Render might be continuing to try and serve traffic to the old service instance (web-6d667) after it had given it the shutdown signal. If that is true, it is continuing to do this behavior for 20+ seconds after the old service instance was told to shutdown.

Subjectively, this feels correct based on what I have observed. During the deploy, I was rapidly hitting refresh and saw the old version, then consistent 502 errors, then some 502 errors interspersed with the new version, then finally, the new version was fully live and everything worked great.

Does my conclusion seem right? Let me know if this helps or if there is anything else I can add.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.