Thanks for the prompt reply. @BYK
I tried few of your answers and some solutions on github issues. Most of them are stale issues and are already fixed in the latest master which we are using.
Since 20.7.0, we require Relay to be running as it is now the only point for ingesting events. You’d need to add this to your mix. See our nginx file for a sample configuration:
I’ve installed directly from getsentry/onpremise on an EC2 instance on AWS, which is behind a WAF.
Everything works fine when I access and browse Sentry through https://my-sentry.company.com, except POST requests, which are always returning a 403.
I’m pretty sure this has to do with my setup, as tunneling to the EC2 instance and configuring Sentry’s Root URL to localhost and accessing Sentry through localhost works perfectly fine.
Here are my configs:
config.yml
system.url-prefix: 'https:/…
getsentry:master ← getsentry:byk/fix/nginx-proxy-header
opened 01:42PM - 01 May 20 UTC
Fixes #447.
This patch should also fix issuer regarding large uploads such as… minidumps by turning off any buffering.
Not sure how to proceed from here.