[Problem] Deploying Sentry with Plesk

On-Premise
1

I have deployed sentry using docker-compose and following the steps mentioned here:
GitHub - getsentry/self-hosted: Sentry, feature-complete and packaged up for low-volume deployments and proofs-of-concept

I created a subdomain in Plesk and associated a lets-encrypt certificate. After that,
I set the SENTRY_USE_SLL env var and build my containers for changes to take place.

After that, under Apache & nginx settings > Additional nginx directives I pasted the following:

set_real_ip_from 127.0.0.1;
set_real_ip_from 10.0.0.0/8;
real_ip_header X-Forwarded-For;
real_ip_recursive on;

ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS;
ssl_prefer_server_ciphers on;
ssl_session_cache shared:SSL:128m;
ssl_session_timeout 10m;

keepalive + raven.js is a disaster

keepalive_timeout 0;

use very aggressive timeouts

proxy_read_timeout 5s;
proxy_send_timeout 5s;
send_timeout 5s;
resolver_timeout 5s;
client_body_timeout 5s;

buffer larger messages

client_body_buffer_size 100k;

proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_redirect off;

location ~ ^/.well-known {
root /var/www/vhosts/my_server_name/subdomains/sentry/;
}

location ~ ^/.* {
proxy_pass http://0.0.0.0:9000;
add_header Strict-Transport-Security “max-age=31536000”;
}

The sentry server is available under https on my subdomain. Everything is fine.
The problem is when I try to sent a test message from my Django application, I dont see it in the dashboard at all:

python3 manage.py raven test
Client configuration:
base_url : https://my_server.com
project : 1
public_key : 2635eacae5464e81b53d358dcc261652
secret_key : 6f505220200b4256b1f98854b8779620

Sending a test message… Event ID was ‘fda69021902247829b65f6e0c3ab70cd’

After tinkering a while, I managed to receive a message by setting the transport setting inside RAVEN_CONFIG to RequestsHTTPTransport.

Obviously, there is something not correct with my nginx configuration.
Has anyone a similar working deployment? And if yes, mind sharing the nginx settings?

Thanks in advance