Native MacOS and iOS app not working with latest vaultwarden release? #1175

New Issue

OVERLORD · 2026-02-05T00:14:12+03:00

OVERLORD commented

2026-02-05 00:14:12 +03:00

Originally created by @Vip0r on GitHub (Dec 26, 2021).

Subject of the issue

Even with the latest vaultwarden image the native mac os and iOS app seems no more working (can't sync the vault).
If i logout and try to re-logon i got the error "failed to fetch data"

WebLogon is working and also the browser-integration is working properly

Deployment environment

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c48444bae464 vaultwarden/server:latest "/usr/bin/dumb-init …" 2 months ago Up 43 minutes (healthy) 80/tcp, 3012/tcp vaultwarden
7609f88915f9 nginx:1.15-alpine "nginx -g 'daemon of…" 12 months ago Up 43 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp bitwarden_nginx_1
(please ignore created - timestamp ; i already also tried to pull the latest img)

Steps to reproduce

upgraded the ios/mac app to the latest version

Tried to re-setup my containers without success. Can you confirm if the latest vaultwarden image should work with the current iOS&macOS native apps (

MacOS Version (Version 1.30.0 (1935))
iOS Version (Version 2.15.0 (1225)

Originally created by @Vip0r on GitHub (Dec 26, 2021). ### Subject of the issue Even with the latest vaultwarden image the native mac os and iOS app seems no more working (can't sync the vault). If i logout and try to re-logon i got the error "failed to fetch data" WebLogon is working and also the browser-integration is working properly ### Deployment environment CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c48444bae464 vaultwarden/server:latest "/usr/bin/dumb-init …" 2 months ago Up 43 minutes (healthy) 80/tcp, 3012/tcp vaultwarden 7609f88915f9 nginx:1.15-alpine "nginx -g 'daemon of…" 12 months ago Up 43 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp bitwarden_nginx_1 (please ignore created - timestamp ; i already also tried to pull the latest img) ### Steps to reproduce upgraded the ios/mac app to the latest version Tried to re-setup my containers without success. Can you confirm if the latest vaultwarden image should work with the current iOS&macOS native apps ( MacOS Version (Version 1.30.0 (1935)) iOS Version (Version 2.15.0 (1225)

OVERLORD closed this issue

2026-02-05 00:14:17 +03:00

OVERLORD commented

2026-02-05 00:14:19 +03:00

@BlackDex commented on GitHub (Dec 26, 2021):

I just quickly tested it on iOS, and that seems to work just fine.
Could you check the logs during the time you try to sync?
Also check the reverse proxy.

@BlackDex commented on GitHub (Dec 26, 2021): I just quickly tested it on iOS, and that seems to work just fine. Could you check the logs during the time you try to sync? Also check the reverse proxy.

OVERLORD commented

2026-02-05 00:14:24 +03:00

@Vip0r commented on GitHub (Dec 26, 2021):

I just quickly tested it on iOS, and that seems to work just fine.
Could you check the logs during the time you try to sync?
Also check the reverse proxy.

Thanks for testing. Maybe there is an issue with my ssl cert. Got the following if try to test the connection with open_ssl:

openssl s_client -showcerts -connect vault.ndnet:443 -servername vault.ndnet .... verify error:num=20:unable to get local issuer certificate

Will check that and provide feedback

@Vip0r commented on GitHub (Dec 26, 2021): > I just quickly tested it on iOS, and that seems to work just fine. > Could you check the logs during the time you try to sync? > Also check the reverse proxy. Thanks for testing. Maybe there is an issue with my ssl cert. Got the following if try to test the connection with open_ssl: ` openssl s_client -showcerts -connect vault.ndnet:443 -servername vault.ndnet .... verify error:num=20:unable to get local issuer certificate` Will check that and provide feedback

OVERLORD commented

2026-02-05 00:14:27 +03:00

@Vip0r commented on GitHub (Dec 26, 2021):

I am prette sure this is related to an expired ssl cert. I have renewed the self signed cert and updated the cert/key files used by nginx.

If i trust the cert on my macbooks i can browse via safari without any issues. After adding the intermediate (CA-Cert) to the nginx webserver i now also get a sucessful output from the openssl test-command:

CONNECTED(00000005) depth=1 CN = 10.0.0.1 verify error:num=19:self signed certificate in certificate chain verify return:0

@Vip0r commented on GitHub (Dec 26, 2021): I am prette sure this is related to an expired ssl cert. I have renewed the self signed cert and updated the cert/key files used by nginx. If i trust the cert on my macbooks i can browse via safari without any issues. After adding the intermediate (CA-Cert) to the nginx webserver i now also get a sucessful output from the openssl test-command: `CONNECTED(00000005) depth=1 CN = 10.0.0.1 verify error:num=19:self signed certificate in certificate chain verify return:0`

OVERLORD commented

2026-02-05 00:14:30 +03:00

@Vip0r commented on GitHub (Dec 26, 2021):

As i am pretty sure that this is issue is somehow related to my own setup i will close this and move this to discussions.

@Vip0r commented on GitHub (Dec 26, 2021): As i am pretty sure that this is issue is somehow related to my own setup i will close this and move this to discussions.

OVERLORD referenced this issue

2026-02-05 05:01:43 +03:00

[PR #1175] [CLOSED] Set tcp ports via environment variables in Dockerfile #2877

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#1175