Troubleshooting Devolutions Password Manager browser extension disconnects
If the Devolutions Password Manager browser extension unexpectedly signs you out of Devolutions Cloud or Devolutions Server, this article explains what the disconnect banner means and what to check.
Look for the disconnect banner:

Compare the reason shown in the banner with the table below, then select the corresponding reason to go directly to its explanation and recommended troubleshooting steps.
Devolutions Cloud
Disconnected - Session expired
Disconnected - Force prompt login
Your SSO provider signed you out. Please reconnect to continue.
You have been disconnected due to inactivity.
Disconnected - The user is disabled
Disconnected - Unable to refresh the current token or obtain a new one.
Disconnected - Unable to refresh the current token or obtain a new one. Show details
Devolutions Server
You have been disconnected due to a server configuration or administrator action, please contact your administrator for more details. Show details
Your SSO provider signed you out. Please reconnect to continue.
You have been disconnected due to inactivity.
Disconnected - Force prompt login
Disconnected - Unable to refresh the current token or obtain a new one.
Disconnected - Unable to refresh the current token or obtain a new one. Show details
Ambiguous disconnect causes
These disconnects do not have a fixed error code or description, so the displayed message may not accurately identify the underlying cause.
To debug this category of disconnect, click Show details and compare the error and error description with the entries below.


invalid_grant
The authorization associated with the refresh token is no longer valid.
Extension-specific disconnect causes
Invalid token after token refresh
This happens when the token refresh succeeds, but the next call returns a 401 error saying that the new token is invalid. To avoid an infinite loop, the browser extension disconnects.
Error during token refresh
This happens when a non-success status is returned during a token refresh. The exact non-success status appears as an error under Show details.
Last updated
Was this helpful?