1Password no loger works

Hello,

Thank you for contacting us regarding this matter.

This is a known issue on our side, and our developers are currently working on a fix. We will notify you as soon as the fix has been released.

Best regards,

Adding a +1 here to monitor for a fix - same issue as OP.

Hello,

Could you please specify which MFA you're using? We haven't been able to reproduce this error internally, so that could help accelerate the situation.

Thank you

I am using Authenticator App MFA (2FAS app).

Ok thank you. I don't have any issues with 2FAS either, so we'll keep digging and let you know once we find anything.

Regards

I'm using the authenticator app as well, but with TOTP.

Hello,

Although we couldn't replicate it, we will have a fix that should resolve this issue in 2026.1.11.0.

Please let us know if your encounter any other problems.

Regards

Once the fix releases, I will test and report back.

@Jonathan Del Signore - is there an ETA on release for the .11 release? The link showing that it is fixed goes to release notes but still at .10?

Hello,

Yes sorry it wasn't out yet, but version 2026.1.11 is now available.

Regards

@Jonathan Del Signore - UPDATE - the newest release 2026.1.11 fixed the 1Password issue for me. Hopefully, that addresses others.

Confirmed working for us too.

Since today we are experiencing the "Login to 1Password failed" error message. We are connecting to 1password with the service account login method.
As we were working with a little older version of RDM (2025.3.28.0) we hoped that updating to 2026.1.14.0 would help, but unfortunately that did not change anything.

The service account token does work in another application (connecting from Ansible for example). Anyone getting the same error when using a service account to connect to 1password?

I'm encountering the exact same issue since yesterday afternoon using 1Password with a 1Password Service Account.

We were also using an older version (v2025.2.29.0) when the issue started and upgrading v2026.1.14.0 did not resolve the issue.

PasswordManagerAccess.Common.InternalErrorException: Invalid or unexpected response from the server (HTTP status: InternalServerError)
 ---> System.Text.Json.JsonException: The input does not contain any JSON tokens. Expected the input to start with a valid JSON token, when isFinalBlock is true. Path: $ | LineNumber: 0 | BytePositionInLine: 0.
 ---> System.Text.Json.JsonReaderException: The input does not contain any JSON tokens. Expected the input to start with a valid JSON token, when isFinalBlock is true. LineNumber: 0 | BytePositionInLine: 0.
   at System.Text.Json.ThrowHelper.ThrowJsonReaderException(Utf8JsonReader& json, ExceptionResource resource, Byte nextByte, ReadOnlySpan`1 bytes)
   at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, T& value, JsonSerializerOptions options, ReadStack& state)
   --- End of inner exception stack trace ---
   at System.Text.Json.ThrowHelper.ReThrowWithPath(ReadStack& state, JsonReaderException ex)
   at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, T& value, JsonSerializerOptions options, ReadStack& state)
   at System.Text.Json.JsonSerializer.ReadFromSpan[TValue](ReadOnlySpan`1 json, JsonTypeInfo`1 jsonTypeInfo)
   at System.Text.Json.JsonSerializer.Deserialize[TValue](String json, JsonSerializerOptions options)
   at PasswordManagerAccess.Common.RestClient.DeserializeFromJson[T](String json)
   at PasswordManagerAccess.Common.RestClient.MakeRequestAsync[TContent,TData](String endpoint, HttpMethod method, HttpContent content, Dictionary`2 headers, Dictionary`2 cookies, Int32 maxRedirects, Func`2 deserialize, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at PasswordManagerAccess.OnePassword.Client.GetEncryptedJson[T](String endpoint, AesKey sessionKey, RestClient rest, CancellationToken cancellationToken)
   at PasswordManagerAccess.OnePassword.Client.GetAccountInfo(AesKey sessionKey, RestClient rest, CancellationToken cancellationToken)
   at PasswordManagerAccess.OnePassword.Client.ListAllVaults(Credentials credentials, Keychain keychain, AesKey sessionKey, RestClient rest, CancellationToken cancellationToken)
   at PasswordManagerAccess.OnePassword.Client.ListAllVaults(Session session, CancellationToken cancellationToken)
   at Devolutions.RemoteDesktopManager.Managers.OnePasswordManager.Initialize(ConnectionEngine engine, String username, String password, String accountKey, String uuid, String url, OnePasswordLoginMethod loginMethod)

Thank you for providing the call stack.

We've now had a few reports for the same issue but are still unable to reproduce this with our internal setup. We'll open a ticket to investigate further.

Regards

Hello,

Could you please confirm if the issue with service accounts persists as of today? We had another client with the same error, but it just started working without us doing anything. There might have been an issue server side.

Thanks

Yes I can confirm that the service account item for 1password works again here. Without changing anything...

Yes, it appears the issue is resolved for me now as well, also without changing anything.

Thank you for the confirmation, I just saw that 1Password released a version with bug fixes yesterday so that must be it.

We'll keep an eye open if it ever happens again.

Regards