Google / Authy OTP issue #108

New issue

Closed

opened 2026-02-20 07:59:23 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 07:59:23 -05:00

Owner

Originally created by @jdesnos on GitHub (Oct 6, 2018).

Hello,

First of all, thanks for this lightweight implementation of birwarden, it's so much easier to deploy than the official!

Here is my issue, when i try to enable OTP in my user settings i get the following error

But, if i wait until the next code is generated on my OTP app (Google Authenticator), the old one works.

I don't get much information from log output.

Here is my setup:

Docker on Synology DSM version 17.05.0-ce
Container setup:

docker run -d
--name bitwarden
-v $CONFIG_DIR/Bitwarden/:/data/
-p 3000:80
mprasil/bitwarden:latest

Can you help me ?

Thank you.

Originally created by @jdesnos on GitHub (Oct 6, 2018). Hello, First of all, thanks for this lightweight implementation of birwarden, it's so much easier to deploy than the official! Here is my issue, when i try to enable OTP in my user settings i get the following error ![otpissue](https://user-images.githubusercontent.com/29238040/46573541-1c7d0480-c997-11e8-8f14-c9a62cca8d63.PNG) But, if i wait until the next code is generated on my OTP app (Google Authenticator), the old one works. ![otpworks](https://user-images.githubusercontent.com/29238040/46573616-2fdc9f80-c998-11e8-8280-6d0771d95010.PNG) I don't get much information from log output. ![image](https://user-images.githubusercontent.com/29238040/46573622-4daa0480-c998-11e8-8190-588ad98e008d.png) Here is my setup: - Docker on Synology DSM version 17.05.0-ce - Container setup: docker run -d \ --name bitwarden \ -v $CONFIG_DIR/Bitwarden/:/data/ \ -p 3000:80 \ mprasil/bitwarden:latest Can you help me ? Thank you.

deekerman closed this issue

2026-02-20 07:59:24 -05:00

deekerman commented

2026-02-20 07:59:24 -05:00

Author

Owner

@fbartels commented on GitHub (Oct 6, 2018):

Hi,

I had a similar issue at first. You should check if your server time matches with the time of your client. Preferably you should set up ntp on your server.

@fbartels commented on GitHub (Oct 6, 2018): Hi, I had a similar issue at first. You should check if your server time matches with the time of your client. Preferably you should set up ntp on your server.

deekerman commented

2026-02-20 07:59:24 -05:00

Author

Owner

@jdesnos commented on GitHub (Oct 6, 2018):

Hi,

I just checked time and there was a 25 second gap between the server and my computer.
With NTP set, it works now perfectly.

Thanks!

@jdesnos commented on GitHub (Oct 6, 2018): Hi, I just checked time and there was a 25 second gap between the server and my computer. With NTP set, it works now perfectly. Thanks!