I’ve already explained this on forums and in the support tickets.
https://www.sysadmins.lv/blog-en/the-case-of-sstp-vpn-with-public-certificate-and-error-0x80092013.aspx
For some reason nobody is acknowledging this issue, and it’s been this way since at least 2014. I tried a live chat yesterday regarding this issue since I was getting it again, and I was told to “be patient” and “wait for a ticket response” and that they “are still investigating the issue”. I asked how long they’ve been investigating this (since I’ve been getting it since November and others since 2014) and I could not get a single straight answer out of the GM answering the chat. He kept saying things like “I don’t have an exact date of when the problem will be resolved” and other methods of skirting the question.
There’s nothing you can do about this to actually fix the problem… that’s on their end. Last-night when this was happening to me I just kept trying every 5 or 10 minutes and it eventually worked, which is exactly what has happened in the past every time I’ve ever had this problem. Prior to this, Toomic was trying to assist me on Steam (thank you) but I think he was a bit busy (understandable). I don’t think they necessarily come on so they can assist players so since it isn’t an official channel of support I appreciate it.
I’ve already gone through several modifications to ESET and my computer settings including completely disabling things until I found out it was the error above. Everyone will automatically jump to the “mess with your firewall/antivirus” idea but it’s not actually solving the problem, unfortunately. We need someone at the company to acknowledge this issue and finally deal with it.
You know how when you get the “sign in could not be completed” error it has this link: “dirtybomb.nexon.net/client/known-issues” ? Well this is what that link USED to point to back in November when I first noticed the problem: http://forums.dirtybomb.nexon.net/discussion/1222/known-issues-work-arounds/p1
You can see here that nothing is mentioned about this specific error, but if you advance through the pages of the thread you’ll find that SEVERAL people have been experiencing this error and nothing was done about it. No replies were made and the thread was just locked.
One could argue that the “Authentication Errors” section relates to this, but the average player (and computer user in general) won’t be able to get anything regarding SSL worked out in their head when they see “sign in could not be completed”. Most users have no clue what SSL is or how any of this works. I’ve also seen another error that stated exactly that… “Authentication Error” leading me to believe this is something different.
@RazielWarmonic @stayfreshshoe @Toomic @Smooth
Being able to login is considered a basic, and this issue has existed since at least 2014.
