Sync error with extension v2023.12.0 on Edge #1795

New Issue

Closed

opened 2026-02-05 01:50:07 +03:00 by OVERLORD · 4 comments

OVERLORD commented 2026-02-05 01:50:07 +03:00

Owner

Copy Link

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 <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.30.1 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker image: vaultwarden/server:1.30.1-alpine * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> Microsoft Edge 2023.12.0 has the issue (on 2 computers) Other clients on 2023.10.2 work fine. * Reverse proxy and version: <!-- if applicable --> * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? -->  ### Expected behaviour <!-- Tell us what you expected to happen --> No error message and actual sync. ### Actual behaviour <!-- Tell us what actually happened --> Error and no sync ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->

OVERLORD added the troubleshooting label 2026-02-05 01:50:07 +03:00

OVERLORD closed this issue 2026-02-05 01:50:16 +03:00

OVERLORD commented 2026-02-05 01:50:19 +03:00

Author

Owner

Copy Link

@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

OVERLORD commented 2026-02-05 01:50:25 +03:00

Author

Owner

Copy Link

@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?

OVERLORD commented 2026-02-05 01:50:29 +03:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Dec 10, 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 10, 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.

OVERLORD commented 2026-02-05 01:50:31 +03:00

Author

Owner

Copy Link

@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

OVERLORD referenced this issue 2026-02-05 05:06:09 +03:00

[PR #1795] [MERGED] Adding a SECURITY.md #2974

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

cached-config-operations

test_dylint

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

SSO

Third party

better for forum

bug

bug

documentation

duplicate

enhancement

future Vault

future Vault

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

troubleshooting

wontfix

No Label troubleshooting

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

OVERLORD

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#1795