Guild Wars 2

Ok so long story short-ish, on monday night when I got home from work I attempted to log into my account, password was fine, was prompted for my mobile authentication.. to which the client repeatedly told me was wrong several times. I tried again via the forum and same thing.. incorrect code.
Then it told me my password was wrong so immediately I believe I’ve been hacked and send off a support ticket and change my password to my email addresses and do thorough scans of my laptop.
Tonight on a lark.. I tried to log into the forums via my tablet.. and I get in first time without any trouble, so I boot up my laptop and client – and yeh I log in straight away, code is correct no problems.. and I changed my account password just incase.

I’ve never had this problem with the authenticator before and I’m wondering if this is normal? I’ve spent the last 24 hours in a state of near anxiety waiting for Anet to reply to my ticket (which I’ve now cancelled) but now it seems like a false alarm.
Anyone else had this?

I reported pretty much the same issue – since the patch that changed the launcher to the PoF-design, the authenticator is kinda broken and fails quite often even if you enter the right code.

I’m pretty sure that its a problem at ANet’s side and has nothing to do with hacking attempts or stuff like this.

My guess is that they changed (messed up) the time-window in which codes are valid. So if you enter the code a little bit too early/late it gets declined.

One thing that could help is to make sure your the clock of the device you’re using to generate the code is correct. You could take a look at https://time.is and check if your clock is roughly in sync with it (the time they are displaying is synchronized with an atomic clock). This could reduce the number of declined codes.

I noticed that immediately as well. The server’s time window is off by 10-15 seconds behind the authenticators….. so you wanna wait until the timer is half way on the code generator’s timer before submitting.

starlinvf.1358:

I noticed that immediately as well. The server’s time window is off by 10-15 seconds behind the authenticators….. so you wanna wait until the timer is half way on the code generator’s timer before submitting.

^ This.

I was having similar issues, then noticed it was happening repeatedly if I was entering the code shortly after timer refresh, but was fine if I left it until it was at least a quarter full again before submitting. Something somewhere is not syncing up as it should.