Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server timezone is on UTC so TOTP codes are not working #141

Closed
guerrerotook opened this issue Jun 16, 2021 · 3 comments · Fixed by #161
Closed

Server timezone is on UTC so TOTP codes are not working #141

guerrerotook opened this issue Jun 16, 2021 · 3 comments · Fixed by #161

Comments

@guerrerotook
Copy link

Problem/Motivation

I can't login to my Bitwarden Vault because all the TOTP codes fails because the server timezone is configured in UTC but my home assistant and myself are CEST time zone.

root@a0d7b954-bitwarden:/# dpkg-reconfigure tzdata

Current default time zone: 'Etc/UTC'
Local time is now: Wed Jun 16 07:48:08 UTC 2021.
Universal Time is now: Wed Jun 16 07:48:08 UTC 2021.

Expected behavior

For the TOTP codes to work and be able to login.

Actual behavior

This is what the web UI says:

Invalid TOTP code! Server time: 2021-06-16 07:44:16 UTC.

Steps to reproduce

I don't really know to reproduce this, but having the container for the bitwarden on UTC and your current time zone in any other.

@Eeems
Copy link

Eeems commented Jul 13, 2021

Possibly a duplicate of #12?

@github-actions
Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Aug 13, 2021
@frenck frenck reopened this Aug 21, 2021
@frenck frenck removed the stale There has not been activity on this issue or PR for quite some time. label Aug 21, 2021
@frenck
Copy link
Member

frenck commented Aug 21, 2021

This is probably caused by this add-on running as a service. This needs to be adjusted to application level.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants