-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server returned invalid handshake? #35
Comments
Having the same problem here dunno what happen |
Same problem here :/ 2014-02-12 1:34 GMT+01:00 André Filipe da Silva Bispo <
|
Same issue! Annoying that it's an rtmp issue. |
Happy to see that i'm not alone ! but i'm not sure it's application issue. I have the same problem on my server but, im my personal computer in DEV environement it's work. Difference between serv/dev , one on ubuntu other on windows. If anyone have an idea. Thanks in advance. |
lolTeam is not working i guess its this problem :/ |
You are wrong. Its working |
no its not search a player |
Hey guys. I'm not seeing this error on my end or on LoLTeam. What servers are you on? Could you post more specific steps to reproduce this error or a stack trace? |
Hey, I've noticed this bug just after 4.2 update. every time i try to run the lib, i get this error: Server returned invalid handshake. I've tried on: eune, euw, na br. None worked, all gave the same error. Also, I've also tried to search for ongoing match just after I've noticed with bug via LoLTeam. it wasn't working for some time. but yesterday it started to work. I'm using windows 7, eclipse. Also tomcat 7.0 server isn't working. If need some more additional information, just let me know and i will try provide as much info as i can to get this fixed ;) |
Im looking for a solution, but log dont give a lot of informations |
it's working again for me without code changes. Maybe the platform instability caused this in some way even though I could log in through league client but not leaguelib. |
Its not working for me yet, I've got no idea why. i also can connect to server through client without any problems |
i tried with 10account, some time one work, some time no.... 95% of time is invalid hanshake |
i've also tried 3 accounts in 4 different servers: eune, euw, br and na. only euw works, other gives the same error. That is strange :/ |
hello guys, i wanna let you know, that it started to work on all servers. not sure what that happened... |
This started up again after the 4.17 patch. Any idea if this is in preparation for the October 1st deadline to remove this stuff from your app? |
It still works fine for me. Did you set version to 4.17.xx? |
Yeah, the problem resolved itself after several hours. It looks like it was
|
4.17.xx and it's happening for me. I assume that it's Riot-side, so I guess I'll just wait. |
Error is gone now with no code change. |
It's happening again and it's been like that since friday (or thursday, I can't even remember). Is it possible that riot have changed something on their servers? |
This are the Server data in LoLRtmpsClient.java This are working on my version ;) Riot have changed some endpoints ;) Take a look into my merge request: |
This started happening again for me. It started when 4.20 was released and it has been going on for about a week now, but this time, the problem is only on my production server. On my dev environment, everything seems to work fine. I tried changing endpoints from
to
or
That didn't resolve the issue at all. Even with the changes, it works on my dev but not in production. The exception being thrown is |
I had the same problem desmond, and it was because my mac had oracle jdk, while my server had openjdk. I'm kind of assuming that it had something to do with the JCE jars or whatever. I'd try that and see if that works. Also, be sure to update to prod.na2 |
I have added a pull request that fixes this issue, see: #44 |
Hello,
today lol have been updated to v4.2. from that time I'm getting this error while trying to use this lib: "Server returned invalid handshake". Any ideas why and how to fix this?
The text was updated successfully, but these errors were encountered: