mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #1572] Time issue #1006
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#1006
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 @xgaia on GitHub (Apr 1, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1572
Subject of the issue
My bitwarden instance don't show the right time. I need the right time fr double auth. Any help will be great !
My server time
the bitwarden container time
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
docker-composefile:Steps to reproduce
Run the stack with the
docker-composeon a machine with CET time.Expected behaviour
Admin interface show CET time
Actual behaviour
Admin interface show UTC time
Troubleshooting data
--
@BlackDex commented on GitHub (Apr 1, 2021):
The date and time you posted your self are exactly the same.
@xgaia commented on GitHub (Apr 1, 2021):
The date of the host server and the container are the same (CET), but not the date displayed by the interface (UTC)
@BlackDex commented on GitHub (Apr 1, 2021):
Could you please provide logs during the attempt to use 2FA?
@BlackDex commented on GitHub (Apr 1, 2021):
That doesn't matter. We convert to UTC only for display
@xgaia commented on GitHub (Apr 1, 2021):
aaah, it probably not a problem of time. I'll get the logs and get back to you. Thanks
@xgaia commented on GitHub (Apr 1, 2021):
here is the log
@BlackDex commented on GitHub (Apr 1, 2021):
Just to verify, is the time in your totp device correct?
@xgaia commented on GitHub (Apr 1, 2021):
yes
@BlackDex commented on GitHub (Apr 1, 2021):
Well, i can't think of anything else besides a wrong totp string.
You can't even enable 2fa without validation, so of you did that long before, then something is changed, but there is nothing changed regarding totp at all in the code.
So, i suggest to create a backup just in case, remove your 2fa via the admin interface and re-create the 2fa.
@BlackDex commented on GitHub (Apr 3, 2021):
I have tested this with multiple situations, having the server timezone in US (while i'm in EU), even changed my host timezone (Still in sync with UTC offset). As long as the UTC time is correct, i can login using TOTP.
So i really think you either use a wrong TOTP, or something happened with the database and corrupted that string somehow.