Login can't load in

[DeckerSlain]

I get the login box and i can enter my information but when i get the next screen the game freezes music contiunes to play and an error message pops up. Error box says "Authentication Failed--App will now close" . Anyone know how to fix?

[memison]

Exactly the same issue here. Only started happening within the last 3 days. Starting to get worried my guild will kick me if I can't be active.

[memison]

Bump please

[wargrimnir]

Some people have found Windows Defender to be killing the launcher before it has a chance to run. To solve this, exclude your entire ROR folder from being scanned by it. How to do so should be pretty easy to look up. If Windows already killed it, simply download a fresh one from the website.

Naturally this extends to any antivirus software. If you can add an exclusion to the folder, please do. It will save you some headaches.

[Thoruic]

Cant download fresh from internet because the update has errors and wont continue.

[hphn]

This issue has to be resolved by admins. Trojan inside launcher file is not something simple. Previously it wasn't there, why it's there now? Awaiting for fix

[wargrimnir]

Look up the specific flag for the trojan. It's most likely a generic entry for heuristic scanning. This means whatever AV company scanned our application while it was running, noted that it's doing manipulation in the memory data stream, which is unusual, and flagged it as a virus for being relatively unknown. Once it's added to an AV database, it generally spreads around from there as everyone wants to have the most seriously up to date antivirus possible so the can make fake graphs about how they're a million times better than the other guy despite being 99.9999% the exact same. Basically, the AV companies have become the viruses and anything they can get their hands on becomes corrupted beyond recognition.

The best we can do is petition each company to be removed from their bullshit database, but every time we update the launcher they just flag us again. It will be easier for you in the long run to just whitelist the RoR folder instead of having your game deleted anytime the launcher is updated and some shady bullshit AV deletes it again. Or uninstall your AV and don't click dumb links or open crappy emails...

Pardon the rant. AV companies have been garbage for a solid 10 years now. Having the project affected bothers me more than it should.

[memison]

That *seems* to have sorted it for now. Will update if I have anymore issues. Didn't know it would be the windows security as It never gave me any notifications that it was being blocked.

Many thanks Wargrimnir

[memison]

Nope. Seems to only be an issue intermittently. Still an issue however as I only seem to be able to log in one in ten times.

Have tried disabling the firewall entirely to no avail. It still just crashes with the aforementioned error message.

[thorhogg]

Getting this also, no firewall, no windows defender.

EDIT: IP of the auth server isnt reachable. Traceroute shows the connection getting through my ISP but doesn't make it all the way to the server. Confirmed not an issue with a connection on my end. Again, no firewall or AV active. Running in Admin mode.


[2018/12/15 21:37:03] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2018/12/15 21:37:03] Attempting authentication using session token
[2018/12/15 21:37:03] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2018/12/15 21:37:03] MythLogin::LoginClient::Connect: Attempting connection to 46.105.54.77:8048
[2018/12/15 21:37:03] Active Sockets: Host [0] Client [1]
[2018/12/15 21:37:04] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2018/12/15 21:37:04] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2018/12/15 21:37:19] Active Sockets: Host [0] Client [1]
[2018/12/15 21:37:28] MythLogin::LoginClient::ReportTimeout: Reporting timeout condition for expected reply type: 6
[2018/12/15 21:37:28] MythLogin::LoginClient::HandleAuthSessionTokenReply: Received session auth reply from server
[2018/12/15 21:37:28] MythLogin::LoginClient::HandleAuthSessionTokenReply: Failed to authenticate session. Result: 9
[2018/12/15 21:37:28] œš§: Failed authentication with session token. Result: 4904840
[2018/12/15 21:37:35] Active Sockets: Host [0] Client [1]
[2018/12/15 21:38:01] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2018/12/15 21:38:01] Attempting authentication using session token
[2018/12/15 21:38:01] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2018/12/15 21:38:01] MythLogin::LoginClient::Connect: Attempting connection to 46.105.54.77:8048
[2018/12/15 21:38:01] Active Sockets: Host [0] Client [1]
[2018/12/15 21:38:02] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2018/12/15 21:38:02] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2018/12/15 21:38:17] Active Sockets: Host [0] Client [1]
[2018/12/15 21:38:26] MythLogin::LoginClient::ReportTimeout: Reporting timeout condition for expected reply type: 6
[2018/12/15 21:38:26] MythLogin::LoginClient::HandleAuthSessionTokenReply: Received session auth reply from server
[2018/12/15 21:38:26] MythLogin::LoginClient::HandleAuthSessionTokenReply: Failed to authenticate session. Result: 9
[2018/12/15 21:38:26] œš§: Failed authentication with session token. Result: 4904840
[2018/12/15 22:35:05] Active Sockets: Host [0] Client [1]