I cannot enter into Grist anymore

Ask for Help
1

For some reason I can’t enter grist any longer. I have been running it successfully for a while. My stack is Grist on docker, authentik OIDC, and swag as reverse proxy. i have not changed anything between it running successfully and now. but I did update grist to the latest version as I always do. I get this error:

grist     | RPError: outgoing request timed out after 3500ms
grist     |     at /grist/node_modules/openid-client/lib/helpers/request.js:137:13
grist     |     at async Issuer.discover (/grist/node_modules/openid-client/lib/issuer.js:171:22)
grist     |     at async OIDCConfig._initClient (/grist/_build/app/server/lib/OIDCConfig.js:251:24)
grist     |     at async OIDCConfig.initOIDC (/grist/_build/app/server/lib/OIDCConfig.js:158:9)
grist     |     at async OIDCConfig.build (/grist/_build/app/server/lib/OIDCConfig.js:106:9)
grist     |     at async Object.getMiddleware (/grist/_build/app/server/lib/OIDCConfig.js:340:28)
grist     |     at async FlexServer.addLoginMiddleware (/grist/_build/app/server/lib/FlexServer.js:1182:33)
grist     |     at async MergedServer.create (/grist/_build/app/server/MergedServer.js:86:9)
grist     |     at async main (/grist/_build/stubs/app/server/server.js:139:26)

Thank you.

I should mention, I checked authentik and it is working fine for other applications and I do not see any problems there. I also haven’t changed anything in the nginx (swag) configuration and it looks fine also.

2

What the error is saying is that Grist is unable to reach the IdP URL, the one configured with GRIST_OIDC_IDP_ISSUER environment variable, and documented here: openid-client/docs/README.md at a84d022f195f82ca1c97f8f6b2567ebcef8738c3 · panva/openid-client · GitHub.

I don’t think anything about this call changed on the Grist side recently. This is probably a matter of network configuration between Grist, Authentik, and docker. I can’t be more helpful without more information, but that’s what I would look at.

3

Thank you, yes, it was a strange networking problem