Alex Zaslavsky

Did you run `update-ca-certificates`, or copy the certs in manually? You may still need to run the update script even after a manual copy.

It seems that you've already applied this migration. Is the table `dangerous_but_trivial_idx` empty?

Using the helm charts? If you mean via sentry kubernetes, this is an explicitly unsupported workflow. We only provide support when using the docker-compose based setup described in this repository.

We're working on a fix, which we will try to get out before the next release.

There was a [breaking change](https://develop.sentry.dev/self-hosted/releases/#breaking-changes) at 23.11.0 that removed a server that was not on the default SMTP path. Is it possible that either of you were using it?

@michaelkuty are you seeing the CERITIFICATE_VERIFY_FAILED error as well?

If this is a CPython issue, as indicated by the linked comment, it seems like there's not much for us to do at the moment. It seems like the ideal...

Do you have any server logs (from the `web` container) when these log ins fail? Generally, you'll be looking for a 400 or 403 error.

Do you see anything suspicious in the `web` logs at all? It's odd that it would fail to log users in without leaving any breadcrumbs.

By default, this is the intended effect, since restore needs to work on an already-used database (ex: what if you are restoring into a DB that already has pk `12`?)....