Closed marksitko closed 2 years ago
Routing to @getsentry/team-webplatform for triage. ⏲️
Hi @masinette, hi @marksitko -- this is not something in the scope of the Web team, doesn't seem to be an SDK issue but rather environment / Sentry self-hosted setup. Re-routing.
Routing to @getsentry/open-source for triage. ⏲️
Thanks @rhcarvalho @masinette, transferring to onpremise
repo ...
I changed my SMTP settings in
sentry/config.yml
and then randocker-compose restart
I take it the SMTP settings change is not implicated. From the screenshot it looks like all of the images were created 4 weeks ago so there doesn't seem to be a question of rebuilding images introducing a code change, correct? Did anything else change? Version of Sentry Vue SDK? Anything else on the frontend? 🤔
Yes that's right, there are no code changes so it's not about rebuilding.
Thats the strange think, there is no changes on the frontend or with the Vue SDK.
Installed are @sentry/tracing
@sentry/vue
with version 6.13.3
Since from restarting docker containers it doesn't track anything, you can see it in the screenshot, the last issue is 3 days ago, this was the time at which it was restarted.
I just also found out that tracking for the "internal" project does not work either.
From the logs from sentry_nginx_1
container i found that error message, maybe it helps you to identify the problem
[error] 22#22: *12713 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "POST /api/1/envelope/?sentry_key=<KEY>&sentry_version=7 HTTP/1.0", upstream: "http://172.18.0.25:3000/api/1/envelope/?sentry_key=<KEY>&sentry_version=7", host: "localhost:9000", referrer: "https://sentry.valcom.org/organizations/valcom/projects/"
I suspect there's something wrong with host nginx configuration. Try this: outside of server:
upstream senti {
keepalive 32; # keepalive connections
server 127.0.0.1:9000; # senti ip and port
}
in your server:
location / {
proxy_pass http://senti/;
proxy_redirect default;
proxy_http_version 1.1;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_max_temp_file_size 0;
#this is the maximum upload size
client_max_body_size 10m;
client_body_buffer_size 128k;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffering off;
proxy_request_buffering off; # Required for HTTP CLI commands
}
I did a little bit research and found an post in the sentry form with a solution that helped me out. It may that the kafka forwarder gets into a bad state.
For anyone else run into the same issue, here is the solution that works for me: https://forum.sentry.io/t/sentry-no-more-catch-errors/10500/10
Thanks for helping. Issue can be closed.
Environment
self-hosted (
onpremise
deployment)Version
21.10.0
Steps to Reproduce
View weeks ago i have set up the self-hosted sentry enviornment for my multi tenant app. It is provided with a Laravel backend and a dedicated VueJS Frontend. Everything works fine until i yesterday changed my SMTP settings in
sentry/config.yml
and then randocker-compose restart
. Containers are all started and healthy.My nginx config for the self-hosted sentry server
Expected Result
Requests are not blocked and bug tracking should work as before and as expected.
Actual Result
Every request from the frontend is blocked by cors policy.
Backend also don't track errors anymore. Even from local development or from production.
From the time i ran
docker-compose restart
my sentry dashboard stopped receive new issues.