-
Subject of the issueedit: not sure if I should list this here or at the official Bitwarden Deployment environmentSynology Docker
Steps to reproduceI checked the date on Synology and Docker container, that is correct. Expected behaviourI expect the same generated keys as in Google Authenticator Actual behaviourThey are different and now no longer work as 2FA. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
Hi @opicron, have you changed something in the mean time (if it was working fine before, or it is a new installation) ? You wrote you checked the date, but is the time really correct on second level on all devices (synology, vaultwarden/docker, google auth device) ? And is everything green also under /admin/diagnostics ? |
Beta Was this translation helpful? Give feedback.
-
Please check the |
Beta Was this translation helpful? Give feedback.
-
Thank you for swift response. I think this is correct:
Support string:
|
Beta Was this translation helpful? Give feedback.
-
It looks to me like either server or your host is drifting time. They are too much apart. I'm not sure which is wrong, it could even be both. Try to enable NTP or something on the docker host. |
Beta Was this translation helpful? Give feedback.
-
The synology host is updated by Google NTP. Docker has same time. I now see that only the firefox plugin is incorrect. The iPhone bitwarden shows the correct keys. I would expect that the Firefox plugin doesnt use the local time, I think my expectation is incorrect. I will mark as closed now, especially seeing nobody else is having issues. Sorry. |
Beta Was this translation helpful? Give feedback.
-
@opicron Then it looks like your client (where you are running Firefox on) is not having the correct time as seen there is more then 6 minutes time difference. I would try to enable or verify the NTP state of you client (laptop/desktop/rpi, whatever) |
Beta Was this translation helpful? Give feedback.
@opicron Then it looks like your client (where you are running Firefox on) is not having the correct time as seen there is more then 6 minutes time difference. I would try to enable or verify the NTP state of you client (laptop/desktop/rpi, whatever)