[GH-ISSUE #628] "Preflight respons is not succesful" when logging in Safari extension #423

Closed
opened 2026-03-03 01:28:57 +03:00 by kerem · 18 comments
Owner

Originally created by @mikkelnl on GitHub (Sep 20, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/628

MacOS updates Safari to 13.0, which cause the Bitwarden Safari Extension to stop working. Found out I had to update to Bitwarden 1.16.0 which includes a new extension version for Safari 13.0.

But using this version, I get the response 'Preflight respons is not succesful' when I try to login in the extension. Bitwarden itself/the app is working fine; it connects to my bitwarden_rs.

Any ideas what might cause this, or how to fix it? Thanks!

Originally created by @mikkelnl on GitHub (Sep 20, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/628 MacOS updates Safari to 13.0, which cause the Bitwarden Safari Extension to stop working. Found out I had to update to Bitwarden 1.16.0 which includes a new extension version for Safari 13.0. But using this version, I get the response 'Preflight respons is not succesful' when I try to login in the extension. Bitwarden itself/the app is working fine; it connects to my bitwarden_rs. Any ideas what might cause this, or how to fix it? Thanks!
kerem closed this issue 2026-03-03 01:28:57 +03:00
Author
Owner

@vplme commented on GitHub (Sep 20, 2019):

That should be fixed by https://github.com/dani-garcia/bitwarden_rs/pull/599.

Which version of bitwarden_rs are you running?

<!-- gh-comment-id:533521110 --> @vplme commented on GitHub (Sep 20, 2019): That should be fixed by https://github.com/dani-garcia/bitwarden_rs/pull/599. Which version of bitwarden_rs are you running?
Author
Owner

@mikkelnl commented on GitHub (Sep 20, 2019):

I believe the latest; 1.10.0
And the webvault shows 2.11.0

<!-- gh-comment-id:533522065 --> @mikkelnl commented on GitHub (Sep 20, 2019): I believe the latest; 1.10.0 And the webvault shows 2.11.0
Author
Owner

@vplme commented on GitHub (Sep 20, 2019):

The tagged bitwarden_rs 1.10.0 release (2c2276c) will not contain the fix.

Do you know the exact version from the logging? Example:

bitwarden_1  | /--------------------------------------------------------------------\
bitwarden_1  | |                       Starting Bitwarden_RS                        |
bitwarden_1  | |                      Version 1.10.0-4c07f05b                       |
bitwarden_1  | |--------------------------------------------------------------------|
bitwarden_1  | | This is an *unofficial* Bitwarden implementation, DO NOT use the   |
bitwarden_1  | | official channels to report bugs/features, regardless of client.   |
bitwarden_1  | | Report URL: https://github.com/dani-garcia/bitwarden_rs/issues/new |
bitwarden_1  | \--------------------------------------------------------------------/
<!-- gh-comment-id:533526403 --> @vplme commented on GitHub (Sep 20, 2019): The tagged bitwarden_rs 1.10.0 release (2c2276c) will not contain the fix. Do you know the exact version from the logging? Example: ``` bitwarden_1 | /--------------------------------------------------------------------\ bitwarden_1 | | Starting Bitwarden_RS | bitwarden_1 | | Version 1.10.0-4c07f05b | bitwarden_1 | |--------------------------------------------------------------------| bitwarden_1 | | This is an *unofficial* Bitwarden implementation, DO NOT use the | bitwarden_1 | | official channels to report bugs/features, regardless of client. | bitwarden_1 | | Report URL: https://github.com/dani-garcia/bitwarden_rs/issues/new | bitwarden_1 | \--------------------------------------------------------------------/ ```
Author
Owner

@mikkelnl commented on GitHub (Sep 20, 2019):

Could you explain how/where I can find that info? CMD line command maybe?

<!-- gh-comment-id:533527659 --> @mikkelnl commented on GitHub (Sep 20, 2019): Could you explain how/where I can find that info? CMD line command maybe?
Author
Owner

@mikkelnl commented on GitHub (Sep 20, 2019):

Found it on the /admin page:

Version: 1.10.0-469318bc

<!-- gh-comment-id:533528476 --> @mikkelnl commented on GitHub (Sep 20, 2019): Found it on the /admin page: Version: 1.10.0-469318bc
Author
Owner

@vplme commented on GitHub (Sep 20, 2019):

The version 1.10.0-469318bc is still before the commit that fixed the issue.
So you probably have to update.

<!-- gh-comment-id:533530253 --> @vplme commented on GitHub (Sep 20, 2019): The version `1.10.0-469318bc` is still before the commit that fixed the issue. So you probably have to update.
Author
Owner

@mikkelnl commented on GitHub (Sep 20, 2019):

Thanks for the info, appreciate it... will try to update asap.

<!-- gh-comment-id:533530518 --> @mikkelnl commented on GitHub (Sep 20, 2019): Thanks for the info, appreciate it... will try to update asap.
Author
Owner

@lost-carrier commented on GitHub (Sep 25, 2019):

If anyone is landing here from Google (like me): bitwardenrs/server:1.10.0 might be the latest release (...at the moment), but bitwardenrs/server:latest is even a bit later... ;-)

<!-- gh-comment-id:535212485 --> @lost-carrier commented on GitHub (Sep 25, 2019): If anyone is landing here from Google (like me): ```bitwardenrs/server:1.10.0``` might be the latest release (...at the moment), but ```bitwardenrs/server:latest``` is even a bit later... ;-)
Author
Owner

@mprasil commented on GitHub (Sep 26, 2019):

That's correct, there wasn't yet a numbered release containing the fix. @dani-garcia maybe we should release 1.10.1 as this hits a lot of people that don't want to use latest.

<!-- gh-comment-id:535393032 --> @mprasil commented on GitHub (Sep 26, 2019): That's correct, there wasn't yet a numbered release containing the fix. @dani-garcia maybe we should release 1.10.1 as this hits a lot of people that don't want to use latest.
Author
Owner

@luckydonald commented on GitHub (Oct 4, 2019):

Pulling 1.10.1 did not work.

$ docker pull bitwardenrs/server:1.10.1
Error response from daemon: manifest for bitwardenrs/server:1.10.1 not found
<!-- gh-comment-id:538570951 --> @luckydonald commented on GitHub (Oct 4, 2019): Pulling 1.10.1 did not work. ```bash $ docker pull bitwardenrs/server:1.10.1 Error response from daemon: manifest for bitwardenrs/server:1.10.1 not found ```
Author
Owner

@mprasil commented on GitHub (Oct 5, 2019):

@luckydonald that version wasn't released. You'll have to use latest for now.

<!-- gh-comment-id:538622245 --> @mprasil commented on GitHub (Oct 5, 2019): @luckydonald that version wasn't released. You'll have to use latest for now.
Author
Owner

@luckydonald commented on GitHub (Oct 24, 2019):

Could you guys cut a bugfix release for this bugfix please?

<!-- gh-comment-id:545791433 --> @luckydonald commented on GitHub (Oct 24, 2019): Could you guys cut a bugfix release for this bugfix please?
Author
Owner

@dani-garcia commented on GitHub (Oct 24, 2019):

Version 1.11.0 was released two weeks ago and should contain the fix already
https://github.com/dani-garcia/bitwarden_rs/releases/tag/1.11.0

<!-- gh-comment-id:546045466 --> @dani-garcia commented on GitHub (Oct 24, 2019): Version 1.11.0 was released two weeks ago and should contain the fix already https://github.com/dani-garcia/bitwarden_rs/releases/tag/1.11.0
Author
Owner

@xthursdayx commented on GitHub (Nov 7, 2019):

I'm still having this problem with the most recent version of Safari and Bitwarden... I'm using a custom BW server, if that matters.

<!-- gh-comment-id:551155371 --> @xthursdayx commented on GitHub (Nov 7, 2019): I'm still having this problem with the most recent version of Safari and Bitwarden... I'm using a custom BW server, if that matters.
Author
Owner

@luckydonald commented on GitHub (Nov 8, 2019):

@xthursdayx Yes that matters.
Upgrade to the latest bitwarden_rs, or merge the changes made here into your custom version.

<!-- gh-comment-id:551325254 --> @luckydonald commented on GitHub (Nov 8, 2019): @xthursdayx Yes that matters. Upgrade to the latest `bitwarden_rs`, or merge the changes made here into your custom version.
Author
Owner

@xthursdayx commented on GitHub (Nov 8, 2019):

@xthursdayx Yes that matters.
Upgrade to the latest bitwarden_rs, or merge the changes made here into your custom version.

Oops, apologies, I should have been more clear about what I meant - that I was running this as a docker container. However I just checked the Docker Hub page for the image I was using (https://hub.docker.com/r/mprasil/bitwarden/) and noticed that it has been depreciated in favor of https://hub.docker.com/r/bitwardenrs/server, so I will update my docker accordingly.

<!-- gh-comment-id:551367707 --> @xthursdayx commented on GitHub (Nov 8, 2019): > @xthursdayx Yes that matters. > Upgrade to the latest `bitwarden_rs`, or merge the changes made here into your custom version. Oops, apologies, I should have been more clear about what I meant - that I was running this as a docker container. However I just checked the Docker Hub page for the image I was using (https://hub.docker.com/r/mprasil/bitwarden/) and noticed that it has been depreciated in favor of https://hub.docker.com/r/bitwardenrs/server, so I will update my docker accordingly.
Author
Owner

@luckydonald commented on GitHub (Nov 10, 2019):

Lel, I think I used that one previously as well.

<!-- gh-comment-id:552241639 --> @luckydonald commented on GitHub (Nov 10, 2019): Lel, I think I used that one previously as well.
Author
Owner

@dani-garcia commented on GitHub (May 13, 2020):

Closed due to inactivity.

<!-- gh-comment-id:628278272 --> @dani-garcia commented on GitHub (May 13, 2020): Closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#423
No description provided.