starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00
Code Issues 39 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #5016] An error occured on iOS #2051

New issue
Closed
opened 2026-03-03 02:14:49 +03:00 by kerem · 29 comments
kerem commented 2026-03-03 02:14:49 +03:00
Owner
Copy link

Originally created by @imp1sh on GitHub (Oct 1, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5016

Vaultwarden Support String

Your environment (Generated via diagnostics page)

  • Vaultwarden version: v1.30.5
  • Web-vault version: v2024.1.2b
  • OS/Arch: linux/x86_64
  • Running within a container: true (Base: Debian)
  • Environment settings overridden: true
  • Uses a reverse proxy: true
  • IP Header check: true (X-Real-IP)
  • Internet access: true
  • Internet access via a proxy: false
  • DNS Check: true
  • Browser/Server Time Check: true
  • Server/NTP Time Check: true
  • Domain Configuration Check: true
  • HTTPS Check: true
  • Database type: SQLite
  • Database version: 3.44.0
  • Clients used:
  • Reverse proxy and version:
  • Other relevant information:

Config (Generated via diagnostics page)

Show Running Config

Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ADMIN_TOKEN, SMTP_HOST, SMTP_SSL, SMTP_PORT, SMTP_FROM, SMTP_USERNAME, SMTP_PASSWORD

{
  "_duo_akey": null,
  "_enable_duo": false,
  "_enable_email_2fa": false,
  "_enable_smtp": true,
  "_enable_yubico": true,
  "_icon_service_csp": "",
  "_icon_service_url": "",
  "_ip_header_enabled": true,
  "_smtp_img_src": "cid:",
  "admin_ratelimit_max_burst": 3,
  "admin_ratelimit_seconds": 300,
  "admin_session_lifetime": 20,
  "admin_token": "***",
  "allowed_iframe_ancestors": "",
  "attachments_folder": "data/attachments",
  "auth_request_purge_schedule": "30 * * * * *",
  "authenticator_disable_time_drift": false,
  "data_folder": "data",
  "database_conn_init": "",
  "database_max_conns": 10,
  "database_timeout": 30,
  "database_url": "***************",
  "db_connection_retries": 15,
  "disable_2fa_remember": false,
  "disable_admin_token": false,
  "disable_icon_download": false,
  "domain": "*****://*************",
  "domain_origin": "*****://*************",
  "domain_path": "",
  "domain_set": true,
  "duo_host": null,
  "duo_ikey": null,
  "duo_skey": null,
  "email_attempts_limit": 3,
  "email_change_allowed": true,
  "email_expiration_time": 600,
  "email_token_size": 6,
  "emergency_access_allowed": true,
  "emergency_notification_reminder_schedule": "0 3 * * * *",
  "emergency_request_timeout_schedule": "0 7 * * * *",
  "enable_db_wal": true,
  "event_cleanup_schedule": "0 10 0 * * *",
  "events_days_retain": null,
  "experimental_client_feature_flags": "fido2-vault-credentials",
  "extended_logging": true,
  "helo_name": null,
  "hibp_api_key": null,
  "icon_blacklist_non_global_ips": true,
  "icon_blacklist_regex": null,
  "icon_cache_folder": "data/icon_cache",
  "icon_cache_negttl": 259200,
  "icon_cache_ttl": 2592000,
  "icon_download_timeout": 10,
  "icon_redirect_code": 302,
  "icon_service": "internal",
  "incomplete_2fa_schedule": "30 * * * * *",
  "incomplete_2fa_time_limit": 3,
  "invitation_expiration_hours": 120,
  "invitation_org_name": "Vaultwarden",
  "invitations_allowed": true,
  "ip_header": "X-Real-IP",
  "job_poll_interval_ms": 30000,
  "log_file": null,
  "log_level": "Info",
  "log_timestamp_format": "%Y-%m-%d %H:%M:%S.%3f",
  "login_ratelimit_max_burst": 10,
  "login_ratelimit_seconds": 60,
  "org_attachment_limit": null,
  "org_creation_users": "",
  "org_events_enabled": false,
  "org_groups_enabled": false,
  "password_hints_allowed": true,
  "password_iterations": 100000,
  "push_enabled": false,
  "push_identity_uri": "https://identity.bitwarden.com",
  "push_installation_id": "***",
  "push_installation_key": "***",
  "push_relay_uri": "https://push.bitwarden.com",
  "reload_templates": false,
  "require_device_email": false,
  "rsa_key_filename": "data/rsa_key",
  "send_purge_schedule": "0 5 * * * *",
  "sendmail_command": null,
  "sends_allowed": true,
  "sends_folder": "data/sends",
  "show_password_hint": false,
  "signups_allowed": false,
  "signups_domains_whitelist": "",
  "signups_verify": true,
  "signups_verify_resend_limit": 6,
  "signups_verify_resend_time": 3600,
  "smtp_accept_invalid_certs": false,
  "smtp_accept_invalid_hostnames": false,
  "smtp_auth_mechanism": null,
  "smtp_debug": false,
  "smtp_embed_images": true,
  "smtp_explicit_tls": false,
  "smtp_from": "********************",
  "smtp_from_name": "Vaultwarden - Password Tresor",
  "smtp_host": "**************",
  "smtp_password": "***",
  "smtp_port": 587,
  "smtp_security": "starttls",
  "smtp_ssl": true,
  "smtp_timeout": 15,
  "smtp_username": "*********************",
  "templates_folder": "data/templates",
  "tmp_folder": "data/tmp",
  "trash_auto_delete_days": null,
  "trash_purge_schedule": "0 5 0 * * *",
  "use_sendmail": false,
  "use_syslog": false,
  "user_attachment_limit": null,
  "user_send_limit": null,
  "web_vault_enabled": true,
  "web_vault_folder": "web-vault/",
  "websocket_address": "0.0.0.0",
  "websocket_enabled": true,
  "websocket_port": 3012,
  "yubico_client_id": null,
  "yubico_secret_key": null,
  "yubico_server": null
}

Vaultwarden Build Version

1.30.5

Deployment method

Official Container Image

Custom deployment method

Using Ansible to deploy as podman container

Reverse Proxy

nginx 1.22.1

Host/Server Operating System

Linux

Operating System Version

Debian 12.7

Clients

iOS

Client Version

dunno how to find out on iOS (latest)

Steps To Reproduce

  1. Start iOS client
  2. try to login with Master Password
  3. An error occured

Expected Result

Login should be possible

Actual Result

An error occured message

Logs

reverse proxy logs:

my.domain.net-ssl_access.log:2001:4dd0:2aea:1b:d870:d487:1e4e:3ba0 - - [01/Oct/2024:12:43:35 +0200] "GET /api/devices/knowndevice HTTP/1.1" 200 5 "-" "Bitwarden_Mobile/2024.9.2 (iOS 17.6.1; Model iPhone)"
my.domain.net-ssl_access.log:2001:4dd0:2aea:1b:d870:d487:1e4e:3ba0 - - [01/Oct/2024:12:43:54 +0200] "POST /identity/accounts/prelogin HTTP/1.1" 200 72 "-" "Bitwarden_Mobile/2024.9.2 (iOS 17.6.1; Model iPhone)"

vaultwarden logs
[2024-10-01 10:43:35.233][request][INFO] GET /api/devices/knowndevice
[2024-10-01 10:43:35.233][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK
[2024-10-01 10:43:54.070][request][INFO] POST /identity/accounts/prelogin
[2024-10-01 10:43:54.070][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK

Screenshots or Videos

IMG_20241001_124135_2274

Additional Context

The problem only seem to surface on iOS. Running Linux Desktop Bitwarden client and webgui no problem.

Originally created by @imp1sh on GitHub (Oct 1, 2024). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5016 ### Vaultwarden Support String ### Your environment (Generated via diagnostics page) * Vaultwarden version: v1.30.5 * Web-vault version: v2024.1.2b * OS/Arch: linux/x86_64 * Running within a container: true (Base: Debian) * Environment settings overridden: true * Uses a reverse proxy: true * IP Header check: true (X-Real-IP) * Internet access: true * Internet access via a proxy: false * DNS Check: true * Browser/Server Time Check: true * Server/NTP Time Check: true * Domain Configuration Check: true * HTTPS Check: true * Database type: SQLite * Database version: 3.44.0 * Clients used: * Reverse proxy and version: * Other relevant information: ### Config (Generated via diagnostics page) <details><summary>Show Running Config</summary> **Environment settings which are overridden:** DOMAIN, SIGNUPS_ALLOWED, ADMIN_TOKEN, SMTP_HOST, SMTP_SSL, SMTP_PORT, SMTP_FROM, SMTP_USERNAME, SMTP_PASSWORD ```json { "_duo_akey": null, "_enable_duo": false, "_enable_email_2fa": false, "_enable_smtp": true, "_enable_yubico": true, "_icon_service_csp": "", "_icon_service_url": "", "_ip_header_enabled": true, "_smtp_img_src": "cid:", "admin_ratelimit_max_burst": 3, "admin_ratelimit_seconds": 300, "admin_session_lifetime": 20, "admin_token": "***", "allowed_iframe_ancestors": "", "attachments_folder": "data/attachments", "auth_request_purge_schedule": "30 * * * * *", "authenticator_disable_time_drift": false, "data_folder": "data", "database_conn_init": "", "database_max_conns": 10, "database_timeout": 30, "database_url": "***************", "db_connection_retries": 15, "disable_2fa_remember": false, "disable_admin_token": false, "disable_icon_download": false, "domain": "*****://*************", "domain_origin": "*****://*************", "domain_path": "", "domain_set": true, "duo_host": null, "duo_ikey": null, "duo_skey": null, "email_attempts_limit": 3, "email_change_allowed": true, "email_expiration_time": 600, "email_token_size": 6, "emergency_access_allowed": true, "emergency_notification_reminder_schedule": "0 3 * * * *", "emergency_request_timeout_schedule": "0 7 * * * *", "enable_db_wal": true, "event_cleanup_schedule": "0 10 0 * * *", "events_days_retain": null, "experimental_client_feature_flags": "fido2-vault-credentials", "extended_logging": true, "helo_name": null, "hibp_api_key": null, "icon_blacklist_non_global_ips": true, "icon_blacklist_regex": null, "icon_cache_folder": "data/icon_cache", "icon_cache_negttl": 259200, "icon_cache_ttl": 2592000, "icon_download_timeout": 10, "icon_redirect_code": 302, "icon_service": "internal", "incomplete_2fa_schedule": "30 * * * * *", "incomplete_2fa_time_limit": 3, "invitation_expiration_hours": 120, "invitation_org_name": "Vaultwarden", "invitations_allowed": true, "ip_header": "X-Real-IP", "job_poll_interval_ms": 30000, "log_file": null, "log_level": "Info", "log_timestamp_format": "%Y-%m-%d %H:%M:%S.%3f", "login_ratelimit_max_burst": 10, "login_ratelimit_seconds": 60, "org_attachment_limit": null, "org_creation_users": "", "org_events_enabled": false, "org_groups_enabled": false, "password_hints_allowed": true, "password_iterations": 100000, "push_enabled": false, "push_identity_uri": "https://identity.bitwarden.com", "push_installation_id": "***", "push_installation_key": "***", "push_relay_uri": "https://push.bitwarden.com", "reload_templates": false, "require_device_email": false, "rsa_key_filename": "data/rsa_key", "send_purge_schedule": "0 5 * * * *", "sendmail_command": null, "sends_allowed": true, "sends_folder": "data/sends", "show_password_hint": false, "signups_allowed": false, "signups_domains_whitelist": "", "signups_verify": true, "signups_verify_resend_limit": 6, "signups_verify_resend_time": 3600, "smtp_accept_invalid_certs": false, "smtp_accept_invalid_hostnames": false, "smtp_auth_mechanism": null, "smtp_debug": false, "smtp_embed_images": true, "smtp_explicit_tls": false, "smtp_from": "********************", "smtp_from_name": "Vaultwarden - Password Tresor", "smtp_host": "**************", "smtp_password": "***", "smtp_port": 587, "smtp_security": "starttls", "smtp_ssl": true, "smtp_timeout": 15, "smtp_username": "*********************", "templates_folder": "data/templates", "tmp_folder": "data/tmp", "trash_auto_delete_days": null, "trash_purge_schedule": "0 5 0 * * *", "use_sendmail": false, "use_syslog": false, "user_attachment_limit": null, "user_send_limit": null, "web_vault_enabled": true, "web_vault_folder": "web-vault/", "websocket_address": "0.0.0.0", "websocket_enabled": true, "websocket_port": 3012, "yubico_client_id": null, "yubico_secret_key": null, "yubico_server": null } ``` </details> ### Vaultwarden Build Version 1.30.5 ### Deployment method Official Container Image ### Custom deployment method Using Ansible to deploy as podman container ### Reverse Proxy nginx 1.22.1 ### Host/Server Operating System Linux ### Operating System Version Debian 12.7 ### Clients iOS ### Client Version dunno how to find out on iOS (latest) ### Steps To Reproduce 1. Start iOS client 2. try to login with Master Password 3. An error occured ### Expected Result Login should be possible ### Actual Result An error occured message ### Logs ```text reverse proxy logs: my.domain.net-ssl_access.log:2001:4dd0:2aea:1b:d870:d487:1e4e:3ba0 - - [01/Oct/2024:12:43:35 +0200] "GET /api/devices/knowndevice HTTP/1.1" 200 5 "-" "Bitwarden_Mobile/2024.9.2 (iOS 17.6.1; Model iPhone)" my.domain.net-ssl_access.log:2001:4dd0:2aea:1b:d870:d487:1e4e:3ba0 - - [01/Oct/2024:12:43:54 +0200] "POST /identity/accounts/prelogin HTTP/1.1" 200 72 "-" "Bitwarden_Mobile/2024.9.2 (iOS 17.6.1; Model iPhone)" vaultwarden logs [2024-10-01 10:43:35.233][request][INFO] GET /api/devices/knowndevice [2024-10-01 10:43:35.233][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK [2024-10-01 10:43:54.070][request][INFO] POST /identity/accounts/prelogin [2024-10-01 10:43:54.070][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK ``` ### Screenshots or Videos ![IMG_20241001_124135_2274](https://github.com/user-attachments/assets/d7b043f1-3743-4cd4-b440-b71718b31f92) ### Additional Context The problem only seem to surface on iOS. Running Linux Desktop Bitwarden client and webgui no problem.
kerem 2026-03-03 02:14:49 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@tin607 commented on GitHub (Oct 1, 2024):

me too！

<!-- gh-comment-id:2385474174 --> @tin607 commented on GitHub (Oct 1, 2024): me too！
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 1, 2024):

Try to update to the testing tagged version and let us know if that solves the issue. If so, that would mean we can release a new stable version soon and the issues are fixed.

<!-- gh-comment-id:2385481555 --> @BlackDex commented on GitHub (Oct 1, 2024): Try to update to the `testing` tagged version and let us know if that solves the issue. If so, that would mean we can release a new stable version soon and the issues are fixed.
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@henningkessler commented on GitHub (Oct 1, 2024):

Having the same issue after upgrading to Bitwarden mobil iOS version 2024.9.2 before it was fine...

<!-- gh-comment-id:2385540508 --> @henningkessler commented on GitHub (Oct 1, 2024): Having the same issue after upgrading to Bitwarden mobil iOS version 2024.9.2 before it was fine...
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@imp1sh commented on GitHub (Oct 1, 2024):

Using the testing tag resolves my issue

<!-- gh-comment-id:2385565398 --> @imp1sh commented on GitHub (Oct 1, 2024): Using the `testing` tag resolves my issue
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@jakerobers commented on GitHub (Oct 1, 2024):

I noticed the same issue. Using the testing tag fixed it for me. Thanks!
Also gave it a brief test by doing various CRUD operations through the iOS app and it feels stable.

<!-- gh-comment-id:2385612158 --> @jakerobers commented on GitHub (Oct 1, 2024): I noticed the same issue. Using the `testing` tag fixed it for me. Thanks! Also gave it a brief test by doing various CRUD operations through the iOS app and it feels stable.
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@ErneX commented on GitHub (Oct 1, 2024):

Hi, for those of us building from source, does the latest tag (1.32.0) solves this issue? Thanks in advance.

<!-- gh-comment-id:2386383870 --> @ErneX commented on GitHub (Oct 1, 2024): Hi, for those of us building from source, does the latest tag (1.32.0) solves this issue? Thanks in advance.
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@NSenaud commented on GitHub (Oct 1, 2024):

I can confirm it works for me on testing too 👍

<!-- gh-comment-id:2386447785 --> @NSenaud commented on GitHub (Oct 1, 2024): I can confirm it works for me on `testing` too 👍
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@buscopan160 commented on GitHub (Oct 1, 2024):

Hi, for those of us building from source, does the latest tag (1.32.0) solves this issue? Thanks in advance.

1.32.0 works for me

<!-- gh-comment-id:2386479279 --> @buscopan160 commented on GitHub (Oct 1, 2024): > Hi, for those of us building from source, does the latest tag (1.32.0) solves this issue? Thanks in advance. 1.32.0 works for me
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@tim-hitchins-ekkosense commented on GitHub (Oct 1, 2024):

1.32.0 works for me via proxmox helper scripts

<!-- gh-comment-id:2386546362 --> @tim-hitchins-ekkosense commented on GitHub (Oct 1, 2024): 1.32.0 works for me via proxmox helper scripts
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@ErneX commented on GitHub (Oct 1, 2024):

Just built 1.32.0 from source and the iOS issue is solved. Thank you all.

<!-- gh-comment-id:2386549660 --> @ErneX commented on GitHub (Oct 1, 2024): Just built 1.32.0 from source and the iOS issue is solved. Thank you all.
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@imp1sh commented on GitHub (Oct 1, 2024):

Looking forward to a new container release. Of course I don't want to stick with testing ^^

<!-- gh-comment-id:2386554127 --> @imp1sh commented on GitHub (Oct 1, 2024): Looking forward to a new container release. Of course I don't want to stick with testing ^^
kerem commented 2026-03-03 02:14:51 +03:00
Author
Owner
Copy link

@zurie commented on GitHub (Oct 1, 2024):

1.32. works for me on a self hosted nas with docker

<!-- gh-comment-id:2386679251 --> @zurie commented on GitHub (Oct 1, 2024): 1.32. works for me on a self hosted nas with docker
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@DeluxZ commented on GitHub (Oct 1, 2024):

Running on latest also having this issue. Would be nice to have a new container release 👍🏼 Missing the ability of autofilling my passwords on my iPhone

<!-- gh-comment-id:2386843801 --> @DeluxZ commented on GitHub (Oct 1, 2024): Running on latest also having this issue. Would be nice to have a new container release 👍🏼 Missing the ability of autofilling my passwords on my iPhone
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@ooliver1 commented on GitHub (Oct 1, 2024):

1.32.0 works just fine after updating from 1.27 not working, 1.32 already has a release and has for a month

<!-- gh-comment-id:2387021909 --> @ooliver1 commented on GitHub (Oct 1, 2024): 1.32.0 works just fine after updating from 1.27 not working, 1.32 already has a release and has for a month
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 1, 2024):

Closing this as it looks like it is fixed in testing and will be in the next stable release. Thanks for the info.

<!-- gh-comment-id:2387072115 --> @BlackDex commented on GitHub (Oct 1, 2024): Closing this as it looks like it is fixed in testing and will be in the next stable release. Thanks for the info.
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@Gerardv514 commented on GitHub (Oct 2, 2024):

Try to update to the testing tagged version and let us know if that solves the issue. If so, that would mean we can release a new stable version soon and the issues are fixed.

Looking at their original version, this specific issue would have been resolved with latest rather than testing also. So It doesn’t appear this issue part of any of the lingering issues that were left over from latest 1.32 to testing?

<!-- gh-comment-id:2387316063 --> @Gerardv514 commented on GitHub (Oct 2, 2024): > Try to update to the `testing` tagged version and let us know if that solves the issue. If so, that would mean we can release a new stable version soon and the issues are fixed. Looking at their original version, this specific issue would have been resolved with latest rather than testing also. So It doesn’t appear this issue part of any of the lingering issues that were left over from latest 1.32 to testing?
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 2, 2024):

Try to update to the testing tagged version and let us know if that solves the issue. If so, that would mean we can release a new stable version soon and the issues are fixed.

Looking at their original version, this specific issue would have been resolved with latest rather than testing also. So It doesn’t appear this issue part of any of the lingering issues that were left over from latest 1.32 to testing.

You can't say that with certainty. There were some fixes in testing which have impact on syncing with the new clients. So for some latest would have been fine, where for others they needed testing.

<!-- gh-comment-id:2387704051 --> @BlackDex commented on GitHub (Oct 2, 2024): > > Try to update to the `testing` tagged version and let us know if that solves the issue. If so, that would mean we can release a new stable version soon and the issues are fixed. > > Looking at their original version, this specific issue would have been resolved with latest rather than testing also. So It doesn’t appear this issue part of any of the lingering issues that were left over from latest 1.32 to testing. You can't say that with certainty. There were some fixes in testing which have impact on syncing with the new clients. So for some latest would have been fine, where for others they needed testing.
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@duckdalbe commented on GitHub (Oct 2, 2024):

Just FYI, I'm running 1.32.0 (from the Archlinux package) and still have this problem.

<!-- gh-comment-id:2388687526 --> @duckdalbe commented on GitHub (Oct 2, 2024): Just FYI, I'm running 1.32.0 (from the Archlinux package) and still have this problem.
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 2, 2024):

That isn't using the testing branch, so it might as well not be fixed for you yet.

<!-- gh-comment-id:2388911343 --> @BlackDex commented on GitHub (Oct 2, 2024): That isn't using the `testing` branch, so it might as well not be fixed for you yet.
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@GerryCrooked commented on GitHub (Oct 6, 2024):

how would one use the testing branch without docker? im running it Vaultwarden currently on a dedicated LXC and am not too keen to move everything over to a docker instance

<!-- gh-comment-id:2395237242 --> @GerryCrooked commented on GitHub (Oct 6, 2024): how would one use the testing branch without docker? im running it Vaultwarden currently on a dedicated LXC and am not too keen to move everything over to a docker instance
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 6, 2024):

Just install the latest, as there was a new release just a few days ago

<!-- gh-comment-id:2395311240 --> @BlackDex commented on GitHub (Oct 6, 2024): Just install the latest, as there was a new release just a few days ago
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@uschumac commented on GitHub (Oct 14, 2024):

I have installed 1.32.1 in Docker on my Synology NAS (DS 718+ with DSM 7.1.1-42962 Update 6) But still get the issue with bitwarden release 2024.9.2 on iphone 14 with ios 17.7. Is there something else, I have to do?

<!-- gh-comment-id:2410196924 --> @uschumac commented on GitHub (Oct 14, 2024): I have installed 1.32.1 in Docker on my Synology NAS (DS 718+ with DSM 7.1.1-42962 Update 6) But still get the issue with bitwarden release 2024.9.2 on iphone 14 with ios 17.7. Is there something else, I have to do?
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 14, 2024):

@uschumac you need to install the testing container version which has this fix.

Also, v1.32.2 is the current latest version which does not have the fix for this issue.

<!-- gh-comment-id:2410242945 --> @BlackDex commented on GitHub (Oct 14, 2024): @uschumac you need to install the `testing` container version which has this fix. Also, v1.32.2 is the current latest version which does **not** have the fix for this issue.
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@GerryCrooked commented on GitHub (Oct 14, 2024):

@uschumac you need to install the testing container version which has this fix.

Also, v1.32.2 is the current latest version which does not have the fix for this issue.

Does anyone know if the fix will be included in the next latest version?

<!-- gh-comment-id:2410249237 --> @GerryCrooked commented on GitHub (Oct 14, 2024): > @uschumac you need to install the `testing` container version which has this fix. > > Also, v1.32.2 is the current latest version which does **not** have the fix for this issue. Does anyone know if the fix will be included in the next latest version?
kerem commented 2026-03-03 02:14:52 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 14, 2024):

@GerryCrooked All patches in the main branch will be in the latest version once released, which is always the case.
If you want to test and verify if this works, use the testing tagged container and report back.

<!-- gh-comment-id:2410259323 --> @BlackDex commented on GitHub (Oct 14, 2024): @GerryCrooked All patches in the `main` branch will be in the `latest` version once released, which is always the case. If you want to test and verify if this works, use the `testing` tagged container and report back.
kerem commented 2026-03-03 02:14:53 +03:00
Author
Owner
Copy link

@DeluxZ commented on GitHub (Oct 14, 2024):

For me it's working again with the testing image and iOS 18.0

<!-- gh-comment-id:2410581580 --> @DeluxZ commented on GitHub (Oct 14, 2024): For me it's working again with the `testing` image and iOS 18.0
kerem commented 2026-03-03 02:14:53 +03:00
Author
Owner
Copy link

@uschumac commented on GitHub (Oct 15, 2024):

@BlackDex Thank you for your quick response. I have installed vaultwarden/server -> testing from the repository in my Synology Docker. Unfortunately I still get errors the Username an Password is incorrect. With an iPad with iPadOS 18.01, with an iPhone with iOS 17.7, and a MacBook with MacOS Seqouia 15.01
When looking at the protocol it says, that I have installed 1.32.2 645629a99.
Have I done something wrong?

<!-- gh-comment-id:2413696901 --> @uschumac commented on GitHub (Oct 15, 2024): @BlackDex Thank you for your quick response. I have installed vaultwarden/server -> testing from the repository in my Synology Docker. Unfortunately I still get errors the Username an Password is incorrect. With an iPad with iPadOS 18.01, with an iPhone with iOS 17.7, and a MacBook with MacOS Seqouia 15.01 When looking at the protocol it says, that I have installed 1.32.2 645629a99. Have I done something wrong?
kerem commented 2026-03-03 02:14:53 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 15, 2024):

If it says username/password incorrect that either means the username or password are incorrect, or the user does not exists.

Check the Vaultwarden Admin Backend /admin if the user(s) still exists.
If not, it might be that you are not using the correct volume/storage anymore.
And i have no clue on how that works on a Synology.

<!-- gh-comment-id:2413715533 --> @BlackDex commented on GitHub (Oct 15, 2024): If it says username/password incorrect that either means the username or password are incorrect, or the user does not exists. Check the Vaultwarden Admin Backend `/admin` if the user(s) still exists. If not, it might be that you are not using the correct volume/storage anymore. And i have no clue on how that works on a Synology.
kerem commented 2026-03-03 02:14:53 +03:00
Author
Owner
Copy link

@uschumac commented on GitHub (Oct 15, 2024):

If it says username/password incorrect that either means the username or password are incorrect, or the user does not exists.

Check the Vaultwarden Admin Backend /admin if the user(s) still exists. If not, it might be that you are not using the correct volume/storage anymore. And i have no clue on how that works on a Synology.

@BlackDex Thank you for the quiyk response again. My fault was a wrong entry in the Volumes section. It was docker/vaultwarden/data instead of docker/vaultwarden.

Thanks a lot, now it works again.

<!-- gh-comment-id:2414508766 --> @uschumac commented on GitHub (Oct 15, 2024): > If it says username/password incorrect that either means the username or password are incorrect, or the user does not exists. > > Check the Vaultwarden Admin Backend `/admin` if the user(s) still exists. If not, it might be that you are not using the correct volume/storage anymore. And i have no clue on how that works on a Synology. @BlackDex Thank you for the quiyk response again. My fault was a wrong entry in the Volumes section. It was docker/vaultwarden/data instead of docker/vaultwarden. Thanks a lot, now it works again.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
revert-7033-patch-1
cached-config-operations
test_dylint
1.35.8
1.35.7
1.35.6
1.35.5
1.35.4
1.35.3
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 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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#2051
No description provided.