mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-24 17:12:43 -05:00
[GH-ISSUE #6217] https_proxy only works when specified as IP:Port, not Hostname:Port #11183
Reference in New Issue
Block a user
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 @silentcreek on GitHub (Aug 23, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6217
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
1.34.3
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Caddy 2.10.0
Host/Server Operating System
Linux
Operating System Version
Debian 12.11
Clients
Android
Client Version
2025.8.0 (20577)
Steps To Reproduce
Expected Result
Successful login and access to Vault
Actual Result
Login fails with the error message:
Error getting push token from bitwarden server: error sending request for url
The login via the Web interface works, however.
I also found the solution, which is to replace the hostname of the proxy with its IP address in the environment variable, then it works - see "Additional Context" for more info.
Logs
Screenshots or Videos
No response
Additional Context
I have a Vaultwarden instance that I've been using for more than a year. It's set up behind a reverse proxy as well as a web proxy for http(s) access. It used to work just fine until I recently got logged out of the Bitwarden app on my phone and wanted to log in again. Then I first received the error message, that the push token from the Bitwarden server could not be received. I first suspected a routing or firewall issue, but it turned out to be something else. If I replace the hostname of the proxy server with its IP address, everything works again.
What puzzels me is this:
Please note:
Before I replaced the hostname of the proxy with the IP address, the diagnostics page of the Admin panel world show that Internet Access doesn't work, but all the other tests (including DNS) pass. I think that was not the case when I initially set up aultwarden.