[GH-ISSUE #787] Need Help with Android App #544

New issue

Closed

opened 2026-03-03 01:30:24 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:30:24 +03:00

Owner

Originally created by @Don-Swanson on GitHub (Dec 29, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/787

Subject of the issue

I just setup bitwarden_rs on a fedora server with podman. I am able to access the web vault with the FQDN, and the chrome plugins connect/work just fine with the FQDN. When I try with the android app, I get issues.

I'm sure I'm doing something wrong, but can't figure out what. I've tried using an older version of the android client, but it's not helping.

Your environment

Bitwarden_rs version: 1.13.0-cb6f3927
Install method: docker.io image
Clients used: WebGUI (ok), Chrome Plugin (OK), Android Client (broken)
Reverse proxy and version: Cloudflare & HAProxy 2.18
Other relevant information: command to run:
podman run -d --name bw -p 4000:8080 -p 3012:3012 -v /dock/bitwarden/bwdata_rs/:/data/ -v /dock/bitwarden/bwdata_rs/ssl/keys/:/ssl/ -e ROCKET_WORKERS=30 -e YUBICO_CLIENT_ID=00000 -e YUBICO_SECRET_KEY='000000000000' -e ADMIN_TOKEN='00000' -e SHOW_PASSWORD_HINT=false -e SMTP_HOST=10.1.9.5 -e SMTP_FROM='no-reply@domain.tld' -e SMTP_PORT=25 -e 'DOMAIN'='https://sub.domain.tld/' -e ROCKET_PORT=8080 -e WEBSOCKET_ENABLED=true -e ROCKET_TLS='{certs="/ssl/certificate.crt",key="/ssl/private.key"}' -e SHOW_PASSWORD_HINT=false bitwardenrs/server:latest

Steps to reproduce

Change the Server URL in the Android app then try to login.

Expected behavior

Should login successfully

Actual behavior

With the new app (2.2.8) I get the error typed exactly as displayed (including the duplicate 'to'):
"An error has occurred.
Exception message: Invalid input to
toASCII: sub.domain.tld"

When I try with an old app (2.2.2 or 2.0.4) I get:
"An error has occurred.
There is a problem connecting to the server"

The same issue happens if I try to use the android app to connect directly to the IP and port on the server

Originally created by @Don-Swanson on GitHub (Dec 29, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/787 ### Subject of the issue I just setup bitwarden_rs on a fedora server with podman. I am able to access the web vault with the FQDN, and the chrome plugins connect/work just fine with the FQDN. When I try with the android app, I get issues. I'm sure I'm doing something wrong, but can't figure out what. I've tried using an older version of the android client, but it's not helping. ### Your environment * Bitwarden_rs version: 1.13.0-cb6f3927 * Install method: docker.io image * Clients used: WebGUI (ok), Chrome Plugin (OK), Android Client (broken) * Reverse proxy and version: Cloudflare & HAProxy 2.18 * Other relevant information: command to run: `podman run -d --name bw -p 4000:8080 -p 3012:3012 -v /dock/bitwarden/bwdata_rs/:/data/ -v /dock/bitwarden/bwdata_rs/ssl/keys/:/ssl/ -e ROCKET_WORKERS=30 -e YUBICO_CLIENT_ID=00000 -e YUBICO_SECRET_KEY='000000000000' -e ADMIN_TOKEN='00000' -e SHOW_PASSWORD_HINT=false -e SMTP_HOST=10.1.9.5 -e SMTP_FROM='no-reply@domain.tld' -e SMTP_PORT=25 -e 'DOMAIN'='https://sub.domain.tld/' -e ROCKET_PORT=8080 -e WEBSOCKET_ENABLED=true -e ROCKET_TLS='{certs="/ssl/certificate.crt",key="/ssl/private.key"}' -e SHOW_PASSWORD_HINT=false bitwardenrs/server:latest` ### Steps to reproduce Change the Server URL in the Android app then try to login. ### Expected behavior Should login successfully ### Actual behavior With the new app (2.2.8) I get the error typed exactly as displayed (including the duplicate 'to'): "An error has occurred. Exception message: Invalid input to toASCII: **sub.domain.tld**" When I try with an old app (2.2.2 or 2.0.4) I get: "An error has occurred. There is a problem connecting to the server" The same issue happens if I try to use the android app to connect directly to the IP and port on the server

kerem closed this issue

2026-03-03 01:30:24 +03:00

kerem commented

2026-03-03 01:30:26 +03:00

Author

Owner

@Don-Swanson commented on GitHub (Dec 31, 2019):

I can only conclude that it's an issue with my HAProxy config. I spun it up on my VPS and it works just fine.

@Don-Swanson commented on GitHub (Dec 31, 2019): I can only conclude that it's an issue with my HAProxy config. I spun it up on my VPS and it works just fine.