Have you submitted a support ticket about this? If you have only mentioned it here then you should be aware this is not an official Runbox support forum and our support activities are focused at https://support.runbox.com

Setting the time is crucial as beeboy has said. There is no tolerance outside of the correct 30s period for entering incorrect codes. We may look at this if it affects too many people, but so far only a handful have got in touch with us and in most cases it was a time sychronisation problem.

Have you submitted a support ticket about this? If you have only mentioned it here then you should be aware this is not an official Runbox support forum and our support activities are focused at https://support.runbox.com

Setting the time is crucial as beeboy has said. There is no tolerance outside of the correct 30s period for entering incorrect codes. We may look at this if it affects too many people, but so far only a handful have got in touch with us and in most cases it was a time sychronisation problem.

Yes, I submitted a report several days ago. Added a comment a day ago. No reply.

The same thing is happening with me...my account got hacked, and was used to spam people, so I decided to give the list of one-time passwords a try when support reopened my account and let me reset my password. I thought I would try 2FA at that point, because the e-mail was important to me.I tried using several of the one-time passwords from the printout that I generated when I set the thing up for 2FA.

My main *password* worked fine. None of the half-dozen or so different OTPs or my Unlock Code worked, and so now I'm locked out of my account, with no way of either getting back in or trusting the 2FA process on Runbox ever again.