Error when starting backend

[M-410Gone]

I'm very sorry that it was #138 closed due to my wrong operation.
After I use the instructions you #138 provided, the content displayed on the backend is as shown in the figure

[M-410Gone]

Or is there a manual way to modify the port and password in leagueclient connected? It seems that in the version update in November 2021, the lockfile is no longer used to store tokens and ports, but the running parameters of "leagueclientux. Exe" need to be taken out. Run "wmic process where caption ='leagueclientux. Exe 'get commandline" in CMD.It is not the same as token in the figure.

[sdomi4]

No worries :)
Unfortunately there is no easy way to set this manually. We will look into adding an option with this workaround for the LCU connection, but I can't give you a timeline on how long this will take.

[M-410Gone]

No worries :) Unfortunately there is no easy way to set this manually. We will look into adding an option with this workaround for the LCU connection, but I can't give you a timeline on how long this will take.

Never mind, I can wait for you. If you need help due to regional problems during the repair process, I can help you as much as possible. If you can, please inform me after the repair is completed

[Himyu]

Would you be able to download the newest version and try it again, please?

[M-410Gone]

Would you be able to download the newest version and try it again, please?

Unfortunately, I tried to run the new version at the first time after receiving the message, and the same error still occurred when I ensured that both PowerShell and the game client were running as administrators

[M-410Gone]

Would you be able to download the newest version and try it again, please?

I'm glad I'll tell you a good news! I found a new lockfile file that follows the launch of the game client, and copied the contents to the abandoned lockfile. Fortunately, the back end is running normally, which may be that you need to modify the path to obtain the lockfile file. I can see in the web link that the program is working very hard to obtain the information of the client. However, there is a new problem. As in #113 and #114, "waiting for league client to connect" appears in the back-end content. I tried the solving instructions in #113 and #114, but they didn't seem to work. I used "NPM start - debug - experimentalconnector - leaguepath" C: \ riot \ riot games \ League of Legends "to prompt" not connected to LCU, but distributed to get data ", and" NPM start - debug - experimentalconnector "to prompt" ready connected, Not checking ". Is there another solution? I will continue to try to change the path in the first instruction and try to repair it.

[sdomi4]

As far as I can tell, the backend successfully connected with the alternative lockfile. Do you get events and the UI popping up when entering a champ select?

We will look into adding an option to connect with this alternative method once we find time – for now manually changing the lockfile contents might be a workaround.

[sdomi4]

A possible fix for this should be implemented in the fix-#141 branch. Could you try downloading the tool from the branch and try if this version can connect to your client?

[M-410Gone]

A possible fix for this should be implemented in the fix-#141 branch. Could you try downloading the tool from the branch and try if this version can connect to your client?

I tried to use the tool in #141 branch to link with the alliance client, and it reported a new error, unable to verify the first certificate

[sdomi4]

Sorry, I didn't mention that this should be without the experimental connector (that one still uses the old method).
Could you try with just npm start?

[M-410Gone]

Sorry, I didn't mention that this should be without the experimental connector (that one still uses the old method). Could you try with just npm start?

I'm sorry I didn't understand clearly before After trying NPM start again, it seems to be the correct link? but it's puzzling that the UI still doesn't display correctly on the web page

[sdomi4]

The connection looks good :) The champ select not showing up is probably due to weird PowerShell behavior. Could you try again and make sure nothing is highlighted in PowerShell and you see the small line blinking?

Pressing enter a few times in the PowerShell window also clears that hangup of the console.