Client Saying 'Offline' falsely; Connection Issues???

Crystalicicle·7/11/2017, 7:37:43 PM·15 votes·1,312 views

I have been encountering the issue of getting to the new client log in screen and it saying this exact message in red text: 'We're unable to log you in because you may be offline'. The only issue is I have tried several times to connect and reconnect to my internet; it is unmistakable that I am connected to my wireless connection properly, as I am browsing without issue.

Riot Personnel and fellow summoners; please respond; I have no idea what to do in this situation besides trying to reinstall the client completely, which may take a great deal of time. But in spite of that, I am willing to try any sensible ideas as to fixing this issue.

6 Comments

Vah Naboris7/11/2017, 7:42:39 PM2 votes

it's happening to me too right now, connected to internet with no issues and it is saying I'm offline

UnboundHades7/11/2017, 7:43:27 PM2 votes

same

DonoKyo7/11/2017, 7:52:51 PM2 votes

Same we need a hot fix!

Detatch7/11/2017, 7:56:26 PM1 votes

Same :(

Scripsi7/12/2017, 12:06:13 AM1 votes

This happened to me, except it does this when I'm in the loading screen. For a game.

Hemanth7/12/2017, 6:45:43 AM1 votes

From EUW forum back when it happened to me a few weeks ago

Note: This issue was resolved - if you continue to experience this issue, please contact support for assistance.

Hey everyone,

We're aware of an issue with patch 7.12 that results in this error showing. This will only happen if you relaunch the League Client while already in a game.

To avoid this issue - please do not relaunch your league client while you are in a game.

If you happen to crash out or run into this issue for some reason, there is a workaround you can use in the interim:

Go to C:\Riot Games\League of Legends\Config Open "LeagueClientSettings.yaml" with notepad Find the line: gameflow-patcher-lock:

Delete this whole line Save the file, restart your LoL Client - and you should be able to log in again. We are currently investigating a code fix for this issue, however this should get you around this issue in the interim.

If you received a leaverbuster penalty due to this problem please contact support explaining your issue for our support team to investigate.