diff --git a/docs/organization/authentication/sso/saml2.mdx b/docs/organization/authentication/sso/saml2.mdx
index 3b6eb3bc5a038d..345fe2a0b7a222 100644
--- a/docs/organization/authentication/sso/saml2.mdx
+++ b/docs/organization/authentication/sso/saml2.mdx
@@ -156,3 +156,7 @@ Instead, the member remains inside of Sentry without any means to log in, as the
 #### Attempting to set up SAML2 SSO with an IdP results in a failure with the message “The provider did not return a valid user identity.” What is happening here?
 
 The crux of the problem here is that different IdP platforms (Okta, Azure AD, etc) use different terms and conventions for the fields necessary for the integration to work. As a result, it’s possible to map up incorrect values into Sentry, causing SSO to fail with this error message.
+
+#### API throwing 500 error status when trying to login on self-hosted Sentry
+
+If you're using the self-hosted Sentry, you may encounter this error right after login. Usually this is caused by `system.url-prefix` not being set explicitly on your `sentry/config.yml` file. You need to set it to the URL matching to the web interface of your self-hosted Sentry instance. Then, you may need to execute the `install.sh` script again to apply the changes.