Report this

What is the reason for this report?

NodeJS on an app throws upstream connect error or disconnect/reset before headers. reset reason: connection termination","status":503

Posted on December 16, 2020

Hello guys

I am having a GraphQL server built with nodejs deployed on an application (Not a droplet). I see the server logs this error regularly.

GraphQL Error (Code: 503): {“response”:{“error”:“upstream connect error or disconnect/reset before headers. reset reason: connection termination”,“status”:503}

Any ideas why is this happening frequently?



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

I’m also having this for my api. We can’t process any requests anymore!

Same problem here, after mollie payment forwards me back to my web service. Once i refresh everything works correct.

Anyone found a solution?

This comment has been deleted

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.