-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Error while fetching OpenID metadata stops Synapse from initializing #8088
Comments
To add a bit more info here:
We probably want to retry this a few times with a backoff? Not sure what else we could do. We could also not attempt to load the metadata until someone tries to login, but that seems like it would be much harder to debug. |
While not getting metadata until needed would probably be the cleanest solution, I can understand it being hard to debug. For now, maybe it would be an idea to leave a warning about this somewhere and telling admins to make sure their openid provider is started before synapse? (I've set this up through systemd |
This makes sense if you're running them both on the same system! Might make sense to add a note to https://github.com/matrix-org/synapse/blob/develop/docs/openid.md |
Occurred to me this morning: with synapse 1.28.0. |
The workaround for docker-compose with keycloak in docker is to add a health check. It's a little more complicated, since you need to add a curl binary to the container. And then you can add something like this to your keycloak compose service:
And a dependency in synapse:
|
Description
As the title says, my Synapse instance started crashing once the linked openid provider (selfhosted keycloak) suddenly crashed and began returning 502 errors as you can read in the following log:
Not sure how to properly deal with this, since I'm no expert on either synapse or openid, but it might be a good idea to at least have a catch for 502 errors.
Steps to reproduce
Version information
Version: 1.18.0
Install method: debian package
Quick Edit: This seems to have happened after my server randomly restarted, making it very possible for others to run into a similar issue. If synapse starts before the openid provider, it crashes badly.
The text was updated successfully, but these errors were encountered: