"connection Reset By Peer" Issue

As most people probably know if you are not in 1.8.9 trying to enter a world can result in a "Connection reset by peer" or some other message that kicks you out. Was wondering what is causing this as I was playing in 1.8.9 which does not have Wynn expansion and I lost a damn good Prism because of it (When i logged on all my accessories dropped thankfully saved the other three items). So is the problem client or server side? Can I do anything to fix it or is it out of my control? If it is out of my control is it being patched??

Ps. Sometimes 1.11.2 works sometimes it doesn't no idea why... It was working 4 hours ago but then it stopped working.

Also did i post this in the wrong section this thread creation is hard...
(Edit) I don't get this problem on any other server so I'm convinced it is due to server host location or it is a server side thing.

 

It's a bug. A whole thread was made about it but yet I found it useless. For some people it helps using 1.8 or reseting their server resource packs. I have tried everything and what I think the issue is wynncraft itself. Currently the host has a bad link connection between packets being sent from the receivers and senders.
In translation, if your internet is bad/weak/average/faulty you will often receive this bug.
I have tried using another w-fi which helped, but not in 100% of the chase, unfortunately there is nothing you can do about it from my knowledge. Its a wynncraft related glitch and hopefully they will fix it soon enough.

- What helps me when this happens is finding a freshly restarted server. This way the link is strong without many people interfering with the packets. So in some sense when "other are people online" they rival your connection with wynncraft, thus causing it to "dispatch the carrier" as you are a weak link. "


This shouldn't be the case at all as I found all other servers work perfectly fine. But since wynncraft is such a complex server, it's complexity does not leave out the flaws.

 

@Dalarn
yeah i kinda figured :(
Lets just hope it gets mostly fixed after the code refractor thingy :)