"waiting for LeagueClient to connect"

[JokerOfRage]

Well, the Backend won't connect to the LeagueClient, I tried admin / no admin, I tried reinstalling, doing the --force. No help. This is for EUNE region. I don't know if it is on any other regions as well. I tried firewall off, Admin access to everything. Still doesn't work! Any help is appreciated! Cheer s.

[JokerOfRage]

Also, I tried reinstalling League as well. Cause originally my game was on D drive, I thought that might be the problem. Also no help. Maybe its the new patch.

[Laraakaa]

I don't have any experience with league being installed in another place, so that may cause some issues. Could you try to supply the path to your league of legends installation manually? npm start -- --debug --leaguePath "C:\\Riot Games\League of Legends"

If that does not work, we created another implementation for connecting to the League client, to use that try: npm start -- --debug --experimentalConnector

And if that does still not work, try the other implementation together with the league path: npm start -- --debug --experimentalConnector --leaguePath "C:\\Riot Games\League of Legends"

Make sure that you have your League-Client open before you run the above commands.

Please provide the logs of all the commands above, so we can troubleshoot the issues further. Thank you very much in advance!

[JokerOfRage]

Okay, I did all of these and here are the results.

Prior to this I reinstalled the whole backend and layouts, but while installing backend this was a warning I got:

npm start -- --debug --leaguepath:

Not connected to LCU and can't connect to leagueClient

npm start -- --debug --experimentalConnector

Can't connect to LCU, but also can't conncet / locate leagueClient, also it failed to locate it and asks is it running.

npm start -- --debug --experimentalConnector --leaguePath

Pretty much the same error as in the one prior to this one.

League Client was OPEN during testing, not ran by admin. Windows firewall off as well. Also I am not sure if the LCU was already resolved in one of these issues but this error sounded familiar to me. Love the project btw, hope this helps you. Cheers.

[Laraakaa]

Hey! Thank you for providing the required information. So it looks like it is unable to find the League of Legends client process, and unfortunately then it cannot get around to communicate to it. I can try to apply a fix to the experimental connector, that would skip this step if the leaguePath was provided manually. But first, I wanna make sure of the following things:

1. You are sure that your League of Legends is installed in C:/Riot Games/League of Legends, and not in any other place (you said you installed it on a different location amd then reinstalled it, so just making sure that this is not the issue).
2. What happens when you, during having your client open, open up a powershell prompt (just search for powershell on windows) and enter the following command: WMIC PROCESS WHERE name='LeagueClientUx.exe' GET commandline
3. What version of Windows are you running on? To find out, press Windows + R, then enter winver

Thank you so much for sticking around, let's figure that out!

[JokerOfRage]

No problem at all, here is the info.

1. Yeah, I reinstalled the game under the C directory, I copied the direct League of Legends path and pasted it into the command line.

2. I can't seem to get this command to work, I got this error:

   Node - DESKTOP-B2LQ375
   ERROR:
   Description = Invalid query

   So I opened task manager and pressed right click on every LeagueClient related thing in there and got this path : C:\Riot\Riot Games\League of Legends Keep in mind I used this path when doing all the previous steps where I needed to input "leaguePath"

3. Windows Version: 21H1 (OS BUILD 19043,1052)

[Laraakaa]

Hey, thank you for providing said information!

About point two, I was actually wrong, please excuse. Instead, try opening "Command Prompt" (you can find it in Windows by searching for CMD) and there execute the same command: WMIC PROCESS WHERE name='LeagueClientUx.exe' GET commandline while the league client is open. In the response, please at least redact the "riotclient auth token" as otherwise someone may gain access to your account.

[JokerOfRage]

Hey, no problem as I said :D

Thank you for mentioning to redact the riotclient auth token. Hope this helps you!

[Laraakaa]

Hey! Thank you for providing that. This seems to look fine, I'll try to get something fixed with the experimental connector so we can test further. Will let you know once that is ready.

[Laraakaa]

Hey, I did some changes to the experimental connector that should help us debug the issue further.

First, can you please redownload the whole project? (and go trough installation again).

Then, please execute it like that (while the League Client is open): npm start -- --debug --experimentalConnector --leaguePath "C:\Riot\Riot Games\League of Legends"

This should provide us with more information. Maybe it even works.

Then, I also added more error logging when the error happened with auto detecting the client. So could you maybe also try: npm start -- --debug --experimentalConnector

Thank you in advance!

[JokerOfRage]

Yes!! The issue has been fixed. I reinstalled the program. and ran the npm start -- --debug --experimentalConnector --leaguePath "C:\Riot\Riot Games\League of Legends" command. And it worked!

It also works with the npm start -- --debug --experimentalConnector

Thank you for fixing this issue, also it works on the LATEST ( 11.21 ) patch.

Appreciate your hard work! Have a nice day.