Ok, support is awake (actually we have been since 5 AM UTC this morning, working with analyzing the issue).
Everything should be ok now, but here’s the full disclosure on what happened, and what’s happening.
At around midnight UTC this night something went south with our main server. We do not yet know the exact mechanism, but we have found no indication that it was the result of an external agency or attack.
Now, AxCrypt does not need to talk to our servers once initialized on a device. So, why did this cause problems for you?
One user figured it out – it worked if you disconnect from Internet during sign in.
AxCrypt does not need the servers, but tries to connect. What happened with our server was that it went into twilight mode, neither dead nor alive. It responded to requests, but never completed the response leaving the client hanging.
AxCrypt does not properly handle this situation of answer-but-no-response. That’s a bug. We’ll fix it. We’ll also add an explicit offline mode, so you don’t need to mess with the Internet connection.
Finally, we’ll be investigating and working on the server side issue until it no longer can happen again.
My sincere apologies for the inconvenience, and perhaps some scary moments.