search

drupal-graphql / graphql

GraphQL integration for Drupal 9/10
286 stars 202 forks source link

Failed (104: Connection reset by peer) while reading response header from upstream #1358

Open sarathrajan opened 1 year ago

sarathrajan commented 1 year ago

When the schema increases, getting 502 Bad Gateway error. And the log is as below failed (104: Connection reset by peer) while reading response header from upstream, client: 172.18.0.6, server: , request: "GET /en/admin/config/graphql/servers/manage/test/explorer HTTP/1.1", upstream: "fastcgi://unix:/run/php-fpm.sock:", host: "test.ddev.site", referrer: "https://test.ddev.site/en/admin/config/graphql"

If we remove some of the fields in the schema, site is again up and running.

Anybody facing this issue? Thanks in advance.

c-theriot commented 1 year ago

We ran into this as well. We tried reverting to a previously known "Good" version of our schema, but still saw 502s. When we tried using an empty schema with a single field, our endpoint was up again.

We tried the patch described here: https://github.com/drupal-graphql/graphql/issues/1268, and that seems to have fixed it for us, including being able to use our updated schema that originally gave us 502.

sarathrajan commented 1 year ago

@c-theriot Thanks for the quick response. Yes, this fixed my issue. Hopefully this is not affecting anything in the graphql module workflow.