504 (or 502) http status when deleting a release through API

[romain-raugi]

Self-Hosted Version

25.1.0

CPU Architecture

x86_64

Docker Version

27.5.1

Docker Compose Version

2.32.4

Machine Specification

• My system meets the minimum system requirements of Sentry

Steps to Reproduce

1. Delete a release through the API (https://docs.sentry.io/api/releases/delete-an-organizations-release/)

Expected Result

A response with the http status 204.

Actual Result

Most of the time, responses with http status 504 and 502.

In Nginx logs, this error appears :

2025/02/15 18:17:55 [error] 31#31: *678 upstream prematurely closed connection while reading response header from upstream, client: , server: , request: "DELETE /api/0/organizations//releases// HTTP/1.1", upstream: "http://:9000/api/0/organizations//releases//", host: ":9000"

Event ID

No response

[aldy505]

If you have the exact nginx configuration defined here:

self-hosted/nginx.conf

Lines 23 to 45 in 2f26318

	sendfile on;
	tcp_nopush on;
	tcp_nodelay on;
	reset_timedout_connection on;
	keepalive_timeout 75s;
	gzip off;
	server_tokens off;
	server_names_hash_bucket_size 64;
	types_hash_max_size 2048;
	types_hash_bucket_size 64;
	client_body_buffer_size 64k;
	client_max_body_size 100m;
	proxy_http_version 1.1;
	proxy_redirect off;
	proxy_buffer_size 128k;
	proxy_buffers 4 256k;
	proxy_busy_buffers_size 256k;
	proxy_next_upstream error timeout invalid_header http_502 http_503 non_idempotent;
	proxy_next_upstream_tries 2;

Can you check on your networking side of things? The next culprit might be your Docker networking issue.