mullet.
Accessing application results in 502. "upstream connect error or disconnect/reset before headers. "
Trying to publish an application to the railway platform.
It is a mixture of react, together with some self-built legacy server-side-rendering legacy code.
It has a connection to graphql, which we've allowed through cloudflare already. The same approach worked for other projects.
But as this one is unique in its architecture, we are not able to really put it to work.
It seems to end up in green state, but accessing the webpage just results in
upstream connect error or disconnect/reset before headers. reset reason: protocol error
I thought it might be a http/1.1 vs http/2 issue, but accessing the page with curl, using either of protocols doesn't end in different result.23 replies