Access and SSO
If you're seeing an error page when you try to access Amplitude or log in — or a 500 or 403 error after authenticating with SSO — the questions below cover the most common causes.
What do I do if I'm having an issue logging in with a password?
Try each of these steps:
- Confirm the password is correct. Reset it if you've forgotten.
- Check whether the same problem happens in another browser or in incognito mode. If not, clear your browser's cookies and cache.
- Make sure your browser is up to date. Restart your laptop after updating to make sure the browser fully relaunches, and try again.
- Confirm your browser is supported. See browser compatibility.
- Disable ad blockers and VPNs, or add Amplitude to their allowed list — they can cause Amplitude to behave unexpectedly.
- If you've forgotten your organization's URL, reach out to Amplitude support. They can tell you which organization is associated with your email address.
How do I fix a problem with logging in by SSO?
A common SSO error is a 500 internal server error. This usually means there's a problem with your SAML certificate, and all users in your organization may be affected. To resolve it:
- You need access to the Amplitude platform to upload a new certificate. If you need SSO disabled to log in and fix the problem, contact the Support team.
- Check with your IT team to see if the SAML certificate has expired. If it has, upload a new one.
- Confirm the SAML certificate is correctly formatted. If not, an Amplitude admin should upload a correctly formatted certificate.
Why am I seeing a Google Workspace 403 error on SSO sign-in?
If you've configured SSO via Google Workspace, you may see 403 Error: app_not_enabled_for_user or 403 Error: app_not_configured_for_user:
If you see this error, follow Google Workspace Admin Help for step-by-step instructions.
If these tips don't fix the problem, contact Amplitude support. Include the browser you're using, plus its version, in your request.
Was this helpful?