On screen: There was an unexpected error with the login session. Please try again.
This error is produced locally. It does not appear because the service is down, so the fixes below are worth working through in order.
Session state lives in the Riot Client, not in the League client. When a RiotClientServices.exe process is left hanging after a crash, a forced close or a patch, it holds a dead session handle. The League client then asks it for a token and gets the dead one back.
That is why Riot's own fix consists entirely of killing processes rather than anything network-related.
If killing the processes and signing in again has ever worked for you, it was local. If it survives a clean reboot and the Riot status page shows login or platform problems, or everyone in your region hit it at once right after a patch, it is Riot's side.
Operator documentation: support.riotgames.com. Riot's page is current, last updated 31 May 2026. Note that the old support-leagueoflegends.riotgames.com and support-valorant.riotgames.com domains now redirect into support.riotgames.com/en-us/<game>/, so older links you find elsewhere are stale.
Session state lives in the Riot Client, not in the League client. When a RiotClientServices.exe process is left hanging after a crash, a forced close or a patch, it holds a dead session handle. The League client then asks it for a token and gets the dead one back.
This error is produced locally. It does not appear because the service is down, so the fixes below are worth working through in order.
Start with: Alt+F4 and choose sign out, not exit. This is Riot's own sequence and the distinction matters — exit leaves the session handle in place.