How can I ascertain what caused “Access Token Refresh Error. No refresh token or API keys found. Please try logging out and logging back in” to appear?

Ask the Community Password Manager
, , ,
1

How can I ascertain what caused the undermentioned to appear?

I ask because I experienced it, today, for the first time:

1280×690 51.8 KB

Conducted Diagnosis

All that I observe that is relevant is: [1]

…because of my environment:

            ID: com.bitwarden.desktop
           Ref: app/com.bitwarden.desktop/x86_64/stable
          Arch: x86_64
        Branch: stable
       Version: 2026.3.1
       License: GPL-3.0
        Origin: flathub
    Collection: org.flathub.Stable
  Installation: system
Installed Size: 467.8 MB
       Runtime: org.freedesktop.Platform/x86_64/25.08
           Sdk: org.freedesktop.Sdk/x86_64/25.08

        Commit: fadbbe957ec645f93b734adb28dafd95615676b5128bc848d71ab8eea0c5cdc5
        Parent: dbb33ac96393fb2345e46d8b206eaabf831eb65ce3b39d7233791d678a7b9bf7
       Subject: Merge pull request #316 from flathub/update-master-d870943 (9dbe10fea6fe)
          Date: 2026-04-24 14:09:58 +0000

Consequently, the undermentioned is obviously inapplicable:

  1. forum.manjaro.org/t/187426 ↩︎

2

This Token Access Error x 3 at Login · Issue #18977 · bitwarden/clients · GitHub looks somewhat similar. – And I probably would contact BW support about it – maybe they have an idea.

The Kwallet issue mentions “Syncing failed”. Unfortunately I don’t have any comprehensive list of what could contribute to sync issues, besides the usual troubleshooting list, network/connectivity issues, server outages (like it maybe was the case with this self-hosting server), …??

3

Might also be related to the following?

4

@grb, that certainly looks like the closest-applicable.

@Nail1684, would they be interested?

5

You can always contact BW support “for free”. I think in many cases they can do things (and have insights) we are not able of here in the community forum (i.e. only support can help). In some cases they also collect reports and file bug reports on GitHub if they deem reports as a bug.

So, nothing to lose, really, especially in more tricky or “unclear” cases like this one.

PS: And in some cases, they may also be able to say if this is something that is internally known and/or worked on already.