Unable to setup 2FA due to TZ mismatch about addon-bitwarden

[addons-assistant]

👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull.

[sinclairpaul]

Can you confirm your OS? I would guess its HASSOS? (actually looking at the output I doubt it)

Edit - This doesn't make any sense to me, the timezone should be irrelevant, as the two times are the same. Are you sure this isn't a clock drift issue? Is your HA host using NTP to update its clock? (We have an addon for that btw 😄 )

[dpecos]

The OS from the host is Arch, and I'm running hass.io within a docker container.

I can't tell if it's relevant or not, but based on the linked issue (dani-garcia/vaultwarden#466) I would say it is.

And then, there is indeed a drift of 1 hour between bitwarden containter and the browser I'm using, because of the timezone different, which is not correct, because both boxes are sitting next to the other.

That being said, I'm not 100% confident that this would solve the issue, but at least, IMHO, points in the correct direction.

[sinclairpaul]

Perhaps you could confirm by matching the Timezone on your client device?

[sinclairpaul]

I cannot duplicate this, I still believe the issue is time drift between your server and device (Timezone differences should not impact this, it would be based on UTC).

$ date
Mon Nov 11 13:34:35 EST 2019

$ sudo docker exec -it addon_a0d7b954_bitwarden date
Mon Nov 11 18:34:41 UTC 2019

[dpecos]

I've been able to finally set it up after running ntp on the host machine, so I guess it was indeed a time drift.

Thx for your help and sorry for the misleading issue ¯_(ツ)_/¯

[addons-assistant]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.