When uploading sourcemaps to our privately hosted Sentry instance (Docker, Sentry 8.22) senty-cli often received 502 (Generic error) responses.
We are hosting Sentry behind a reverse proxy, as suggested here:
(I also disabled the keep-alives in Sentry CLI, as suggested later in the thread)
The response being returned from the reverse proxy is either a 502.3 or a 502.6, as we are using IIS as a reverse proxy, we also receive a win32 status code in the IIS log file, which is: 12152 : ERROR_HTTP_INVALID_SERVER_RESPONSE
The actual html responded by the server is also displayed in the sentry-cli output (as it is in info or debug mode), but this is a generic error message by IIS:502 - Web server received an invalid response while acting as a gateway or proxy server.
502 - Web server received an invalid response while acting as a gateway or proxy server.
There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.
Is there any way I can look into the Sentry server logs themselves to analyze this problem?
Just to be clear: this upload does intermittently succeed.