mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #628] "Preflight respons is not succesful" when logging in Safari extension #423
Labels
No 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
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#423
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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!
@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?
@mikkelnl commented on GitHub (Sep 20, 2019):
I believe the latest; 1.10.0
And the webvault shows 2.11.0
@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:
@mikkelnl commented on GitHub (Sep 20, 2019):
Could you explain how/where I can find that info? CMD line command maybe?
@mikkelnl commented on GitHub (Sep 20, 2019):
Found it on the /admin page:
Version: 1.10.0-469318bc
@vplme commented on GitHub (Sep 20, 2019):
The version
1.10.0-469318bcis still before the commit that fixed the issue.So you probably have to update.
@mikkelnl commented on GitHub (Sep 20, 2019):
Thanks for the info, appreciate it... will try to update asap.
@lost-carrier commented on GitHub (Sep 25, 2019):
If anyone is landing here from Google (like me):
bitwardenrs/server:1.10.0might be the latest release (...at the moment), butbitwardenrs/server:latestis even a bit later... ;-)@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.
@luckydonald commented on GitHub (Oct 4, 2019):
Pulling 1.10.1 did not work.
@mprasil commented on GitHub (Oct 5, 2019):
@luckydonald that version wasn't released. You'll have to use latest for now.
@luckydonald commented on GitHub (Oct 24, 2019):
Could you guys cut a bugfix release for this bugfix please?
@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
@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.
@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.@xthursdayx commented on GitHub (Nov 8, 2019):
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.
@luckydonald commented on GitHub (Nov 10, 2019):
Lel, I think I used that one previously as well.
@dani-garcia commented on GitHub (May 13, 2020):
Closed due to inactivity.