starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-02 22:57:18 -05:00

Sync error with extension v2023.12.0 on Edge #1802

New issue

Closed

opened 2026-02-20 08:12:42 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 08:12:42 -05:00

Owner

Originally created by @koying on GitHub (Dec 9, 2023).

Subject of the issue

After the bitwarden extension was auot-updated to 2023.12.0 on Edge, synchornization with v1.30.1 fails.

Deployment environment

vaultwarden version:
1.30.1

Install method:
Docker image: vaultwarden/server:1.30.1-alpine
Clients used:
Microsoft Edge 2023.12.0 has the issue (on 2 computers)
Other clients on 2023.10.2 work fine.
Reverse proxy and version:
MySQL/MariaDB or PostgreSQL version:
Other relevant details:

Steps to reproduce

Expected behaviour

No error message and actual sync.

Actual behaviour

Error and no sync

Troubleshooting data

Originally created by @koying on GitHub (Dec 9, 2023). ### Subject of the issue After the bitwarden extension was auot-updated to 2023.12.0 on Edge, synchornization with v1.30.1 fails. ### Deployment environment     * vaultwarden version: 1.30.1  * Install method: Docker image: vaultwarden/server:1.30.1-alpine * Clients used:  Microsoft Edge 2023.12.0 has the issue (on 2 computers) Other clients on 2023.10.2 work fine. * Reverse proxy and version:  * MySQL/MariaDB or PostgreSQL version:  * Other relevant details: ### Steps to reproduce  ![image](https://github.com/dani-garcia/vaultwarden/assets/164740/3f690f09-a150-40be-a151-158569601cf4) ### Expected behaviour  No error message and actual sync. ### Actual behaviour  Error and no sync ### Troubleshooting data

deekerman

2026-02-20 08:12:42 -05:00

closed this issue
added the
troubleshooting
label

deekerman commented

2026-02-20 08:12:44 -05:00

Author

Owner

@BlackDex commented on GitHub (Dec 9, 2023):

Could you share te logs of Vaultwarden please

@BlackDex commented on GitHub (Dec 9, 2023): Could you share te logs of Vaultwarden please

deekerman commented

2026-02-20 08:12:44 -05:00

Author

Owner

@koying commented on GitHub (Dec 9, 2023):

This is what I see in the docker log when I try a sync:

vaultwarden  | [2023-12-09 10:03:28.923][request][INFO] POST /identity/connect/token
vaultwarden  | [2023-12-09 10:03:28.927][response][INFO] (login) POST /identity/connect/token => 200 OK
vaultwarden  | [2023-12-09 10:03:29.314][request][INFO] GET /api/sync
vaultwarden  | [2023-12-09 10:03:29.384][response][INFO] (sync) GET /api/sync?<data..> => 200 OK

Basically the same as a successful one, it seems.

Is there a way to get some logs from the extension?

@koying commented on GitHub (Dec 9, 2023): This is what I see in the docker log when I try a sync: ``` vaultwarden | [2023-12-09 10:03:28.923][request][INFO] POST /identity/connect/token vaultwarden | [2023-12-09 10:03:28.927][response][INFO] (login) POST /identity/connect/token => 200 OK vaultwarden | [2023-12-09 10:03:29.314][request][INFO] GET /api/sync vaultwarden | [2023-12-09 10:03:29.384][response][INFO] (sync) GET /api/sync?<data..> => 200 OK ``` Basically the same as a successful one, it seems. Is there a way to get some logs from the extension?

deekerman commented

2026-02-20 08:12:44 -05:00

Author

Owner

@BlackDex commented on GitHub (Dec 9, 2023):

This seems to be an extension issue. I was able to reproduce this, but saw nothing strange server-side or client side.

I then fully logged-out of the extension, restarted the browser, logged-in again, and that solved my syncing issue.
I tested this with Chromium, but that is the same extension.

@BlackDex commented on GitHub (Dec 9, 2023): This seems to be an extension issue. I was able to reproduce this, but saw nothing strange server-side or client side. I then fully logged-out of the extension, restarted the browser, logged-in again, and that solved my syncing issue. I tested this with Chromium, but that is the same extension.

deekerman commented

2026-02-20 08:12:44 -05:00

Author

Owner

@koying commented on GitHub (Dec 10, 2023):

Ah, yes. Looks like logout/login makes sync work again, for now at least.
Will report back if the symptom happens again

@koying commented on GitHub (Dec 10, 2023): Ah, yes. Looks like logout/login makes sync work again, for now at least. Will report back if the symptom happens again