League of Legends Down: Riot Games Confirms Login Issues, Fix On the Way

Over the weekend, the League of Legends players faced widespread login issues. As a result, thousands of players across the globe couldn’t access the game. According to reports, the issue was first reported on late Friday, with multiple reports claiming that the Riot Games client didn’t load or authenticate their accounts.

Downdetector, which is one of the most popular outage tracker websites, also showed similar data. Over 7700 user reports were recorded at the time, with most of the reports claiming login issues and frozen clients. Users from North America, Europe, and parts of Asia were affected by the issue.

In a post on X, Riot Games acknowledged the issue and confirmed it was investigating the cause behind it.

While the players were having login issues, League of Legends fans quickly found a possible cause of the issue. Players who dug through error logs and system messages hinted that the issue might be related to an expired SSL client certificate. In simple words, the game’s security certificate was no longer valid, which apparently caused Riot’s system to reject genuine login attempts. Again, this hasn’t been confirmed by Riot Games yet.

As a preventive measure, Riot Games has temporarily disabled ranked cues while the team works on restoring the stability of the client. That being said, Riot’s official status service initially displayed that there were no issues, which eventually added to players’ frustration while the client was out of order.

Many players reportedly also tried common fixes such as reinstalling the client or running Riot’s Hextech Repair tool, but that didn’t solve the problem. Some even shared a temporary but risky workaround. The login issue was apparently resolved after manually setting their system back to January 3, which effectively bypassed the expired certificate. This worked for a few players, but it isn’t recommended by Riot Games.

As of now, there’s no update from the team, but looking at Downdetector data below, it seems the issue has been resolved for now. That said, we still await official confirmation.

Were you also affected by the issue, and if you were, has the workaround solved the problem? Let us know in the comments below.