diff --git a/Enabling-SSO-support-using-OpenId-Connect.md b/Enabling-SSO-support-using-OpenId-Connect.md
index a553a42..9f20783 100644
--- a/Enabling-SSO-support-using-OpenId-Connect.md
+++ b/Enabling-SSO-support-using-OpenId-Connect.md
@@ -153,6 +153,15 @@ Server configuration should look like:
 - `SSO_CLIENT_ID`
 - `SSO_CLIENT_SECRET`
 
+### Troubleshooting
+
+- `Failed to discover OpenID provider: Failed to parse server response`: 
+  - First ensure that the Authority endpoint with `/.well-known/openid-configuration` appended is reacheable.
+  - Next check that the document return `id_token_signing_alg_values_supported: ["RS256"]`\
+    If it returns `HS256` then selecting the default signing key again should fix the issue ([steps](https://github.com/Timshel/vaultwarden/issues/107#issuecomment-3200007338)).
+- `Failed to contact token endpoint: Parse(Error ... Invalid JSON web token: found 5 parts`: \
+ This error is probably due to an encrypted token (JWE), ensure that no encryption key is used ([steps](https://github.com/dani-garcia/vaultwarden/issues/6230#issuecomment-3245196399)).
+
 ## Casdoor
 
 Since version [v1.639.0](https://github.com/casdoor/casdoor/releases/tag/v1.639.0) should work (Tested with version [v1.686.0](https://github.com/casdoor/casdoor/releases/tag/v1.686.0)).