Sentry: All events is empty

Запись создана 25 марта, 2024

If you have a nginx revers proxy on your self-hosted Sentry you can get an issue with empty «All events»

this can be fixed by adding to nginx config

    proxy_buffer_size          128k;
    proxy_buffers    16 256k;

if you need a complete config, here it is:

http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
log_format postdata '$remote_addr - $remote_user [$time_local] '
'"$request" $status $bytes_sent '
'"$http_referer" "$http_user_agent" "$request_body"';

access_log /var/log/nginx/access.log main;
sendfile on;
#tcp_nopush on;
keepalive_timeout 65;
#gzip on;

# set REMOTE_ADDR from any internal proxies
# see http://nginx.org/en/docs/http/ngx_http_realip_module.html
set_real_ip_from 127.0.0.1;
real_ip_header X-Forwarded-For;
real_ip_recursive on;

# SSL configuration -- change these certs to match yours
ssl_certificate /etc/letsencrypt/live/sentry.google.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/sentry.google.com/privkey.pem;

# NOTE: These settings may not be the most-current recommended
# defaults
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;

server {
listen 80;
server_name sentry.google.com;
proxy_set_header Host $http_host;

location / {
if ($request_method = GET) {
rewrite ^ https://$host$request_uri? permanent;
}
return 405;
}
}

server {
listen 443 ssl;
server_name sentry.google.com;

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

# 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_max_body_size 5m;
client_body_buffer_size 100k;

proxy_buffer_size 128k;
proxy_buffers 16 256k;

location / {
proxy_pass http://localhost:9000;

add_header Strict-Transport-Security "max-age=31536000";
}
}
}



			

» Запись из раздела Linux, Nginx | Комментировать

Комментарии





Ответить