Hubert Deng

@yudong5740 Are you using the [docker compose version of self-hosted Sentry](https://github.com/getsentry/self-hosted)?

It's difficult to tell what might be going wrong without additional info. Are there any logs that are useful?

I suspect this may be a proxying issue since it seems that multiple people are only hitting this when using https. Is there any logs in your nginx or web...

> How can i enable the logs for nginx on the docker image? You can just use `docker compose logs web` to find the logs > I did change all...

> I just uncommented the lines for SSL/TLS in sentry.conf.py, changed my nginx config and that's about it. Well, thanks for the data point here. Glad to hear you got...

@WilenChen That is an entirely different issue. That endpoint is internal and is used by admins. You are likely trying to access a page that only superusers can access.

Were you able to get replays working on a previous version of Sentry, or is this the first version where you're seeing this problem?

> I think I see this same issue where replays stop appearing after some time - restarting all containers fixes it - after the restart, containers which were previously missing...

Will do! Let us know what might be going wrong if it happens again.

> Restarting the Kafka, clickhouse and zookeeper containers doesn't seem to solve the issue, but it's fixed again by a full docker compose restart. 4 days worth of replays processed...