Bobby Carp
Bobby Carp
We are unable to reproduce this issue. We suspect it may be related to firewall and/or network settings. Please examine your container configuration to see if you are restricting traffic....
I see. If you find additional info, please re-open with additional logs.
@aamarques I have tried to reproduce this again on our internal self-hosted instance and cannot. The logs you show in your latest message are all HTTP 200. Given the "error...
@aldy505 Sentry internal won't be able to help with this. We would have to know the IP address that is not being considered internal. Unfortunately, there is no easy way...
@balaG4046 Sorry that we haven't been able to help you fix this. As I was looking again at your initial post, it doesn't say exactly what the failure does or...
Assigning to getsentry/sentry for product area triage.
Could you please retry this with 24.11? If it still occurs, could you please provide the detailed error log? Thank you.
The RAM requirements are best-effort recommendation. Trimming the configuration is doable, but I don't think we should try and document requirements for this type of change.
I'm just saying that we wouldn't specify requirements for the different configurations mentioned at https://develop.sentry.dev/self-hosted/#configuration-topics.
@IanWoodard Please reopen if this is still relevant and/or needs investigation.