Closed gioiann closed 5 years ago
This might be fixed on the latest commit thanks to the RakNet changes. Please try it and let me know.
The problem is still there, it just happened again. Also, I don't think the last changes to RakNet affect encryption at all. Packets order affects encryption and that has nothing to do with the latest RakNet changes.
I figured if something was wrong with resending, it could affect this. I also am unable to reproduce it. Do you have a high latency to the server?
There is no way to reproduce it, just randomly happens. I made more tests and only happened once on lbsg when I had a delay of about 450ms (450/3 = 150ms ACK average RTT) But during the tests the delay ranged from 200 to even 500ms at some point and everything was just fine.
By delay i mean the recoveryQueue.AvgDelay * 3
How frequently does this happen at this time?
It isn't happening anymore. I guess it's fixed but I'm not sure as there wasn't a way to reproduce it. I think you can close this issue for now
Alright, thank you. Please do let me know if it happens again!
I've been getting this error really often, expecially on mineplex. When this happens a temporary "fix" is restarting the proxy but eventually it will happen again.
This error message can be either from listener.go or dial.go since it's the same for both. I found out it's from there
So either the server is not encrypting properly (and i don't think so since it works without proxy) or the proxy is doing something wrong.