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

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?

Show comments

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

This comment has been deleted

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

Anyone found a solution?

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