mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #2750] Using send file option logging out consistently #1363
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#1363
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 @dr460nf1r3 on GitHub (Sep 18, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2750
Subject of the issue
Using the send file option triggers a logout.
Deployment environment
Steps to reproduce
testing imageusing the options listed belowExpected behaviour
Actually have the feature working without logout.
Actual behaviour
The user gets logged out.
Troubleshooting data
The relevant log excerpt of when the issue occurred:
@BlackDex commented on GitHub (Sep 18, 2022):
Could you post the support string please?
Because this shouldn't be an issue. Since it should try the v1 directly after. Also check that you do not catch proxy errors within your reverse proxy, that could also cause issues.
@dr460nf1r3 commented on GitHub (Sep 18, 2022):
Sorry, yes of course:
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ADMIN_TOKEN, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY, SMTP_HOST, SMTP_PORT, SMTP_FROM, SMTP_USERNAME, SMTP_PASSWORD
The Nginx error log just contains a 404 on trying to access api v2
@BlackDex commented on GitHub (Sep 18, 2022):
Ok, either
DOMAINis configured incorrectly or you are accessing the admin panel using a different domain then the vault it self. But if that is not the case, then please check the domain settings. These could cause some issues.As for the 404, that shouldn't be an issue, it should just try the v1 after that, unless you catch proxy errors with nginx, which causes the errors to be altered, and then the client API doesn't know what to do next.
Also, check the F12 developer console in the browser if you see at least an attempt, or maybe an other error there.
I just tried it my self on my system both via android client and web-vault, both work as expected