So it looks like there’s a missing file (possibly an avatar) in the filestore and Sentry raises an exception for this. And while it is trying to report that exception to itself, it tries to contact itself via sentry-01.**** using HTTPS and fails due to some proxying issue.
@untitaker are we just using the system.url-prefix in Sentry internal reporting now? Could there be an alternative to that?