mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #1894] Gateway timeout uploading XML on sample proxy configuration #1098
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#1098
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 @melissaboiko on GitHub (Aug 11, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1894
v1.22.2, fresh install, exposed via nginx reverse proxy via configuration from the wiki https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples . The host nginx is 1.14.2, on Debian buster.
When I try to import my Keepass data (at ~2MiB XML), it hangs for a while, then raises an error with nginx giving a 504 proxy timeout. It appears to have nonetheless imported all the data.
I tried increasing the proxy wait time as follows:
and this appears to have been enough, when I looked at the tab again it was back to the main vault page. However, because I didn't realise it was importing the data despite the 504, I ended up with several duplicates of each password.
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Deployment environment
Install method: docker run -d --name bitwarden
-e ADMIN_TOKEN=[token]
-v /vw-data/:/data/
-p 40080:80
vaultwarden/server:latest
Clients used: firefox
Reverse proxy and version: nginx 1.14.2
MySQL/MariaDB or PostgreSQL version:
Other relevant details: Host has 8GiB RAM, amd64 4 cores 3600Mhz and is not under load.
@BlackDex commented on GitHub (Aug 11, 2021):
A 504 is a proxy/gateway timeout, which indicates that its an (configuration) issue of nginx.
Nginx waited for vaultwarden to reply back after the upload, which took a long time, and in the end nginx gave up, but Vaultwarden continued and processed the incoming data.