Inactive Error when logging in

Hi,

I've been having this issue for a few months now and have thought nothing of it. But its become so bad that I can't even connect to the server anymore. Basically, it takes me an AGE to log on. It's stuck on "Downloading Terrain" and it stays like that for about 2 minutes, before I finally connect. When I finally connect, I'm like, stuck in air and my character can't move, then I get disconnected for "Netty Handler and the server was closed by the remote host"

I've tried re-installing Minecraft, changing my RAM allocation, I've even changed the channels on my Wifi. But it only seems to happen to Mineverse. No other server. Any suggestions or help for be greatly appreciated <3

 

Have you tried connecting to another server?

 

I'm pretty sure a restart of the server would fix it. I doubt that will happen for one person sadly :(
Try this:

1). Open your command-prompt (Windows-Key + R)
2). Then type 'CMD' then hit enter
3). Paste this in: netsh interface ipv4 set subinterface "Local Area Connection" mtu=750 store=persistent​

You could also:

1). Try direct-connecting​

Or:

1). Refresh your server-list​

Or:

1). Restart your client & add the server again ​

Or:

1). I'm almost certain this won't work, I cannot imagine IP-forwarding is enabled, but try include the port, so try connect to: 31.220.12.147 or 31.220.12.147:25565​

I hope some of these help resolve your issue.
Best of luck!

​

 

Yes, I can connect to any server but Mineverse. I've always had this issue with taking an AGE to connect to it. I don't suppose that it's my dat file? Since I've been playing for an extremely long time, I might have a lot of data under my user.

 

Try: Skyblock.com

 

Already tried :/

 

Unfortunately no luck :( Guess I'll have to bare it

 

Re-start entire computer or just type the IP you want to directly go on.

 

I'm sorry to hear that.
You could always try unplugging your router for 60 seconds, then plugging it back in. Or unplugging your machine at the wall for 60 seconds. I mean these are the classic 'Have you tried turning it off and on' troubleshooting steps, but they sometimes work.

 

Did you try direct connect?

 

Yep. Tried that too :(

 

Inactive, closing.