Minecraft Forums

This error has become repetitive and obnoxious.

Internal exception: io.netty.handler.timeout.readTimeoutexception

This is my internet speed: http://www.speedtest.net/my-result/3739605448

I am using realms, on 1.8, and Java is Version 7 update 67. (build 1.7.0_67-b01)

My computer is : amd 8 core with 16 gigs, home build

Nvidia GT730 with 2 gigs, driver is 340.52



Everything on every other game runs fine, no matter if its single player on my computer or multiplayer across the net. I play Eve Online and LoL everyday,and I find no issues, I have no issues in SecondLife, a notoriously horrible ap for dropping.

It started in 1.7.1 on a server run by iinet, but it was not extensive or prohibitive, so I chalked it up to something on their end. Now however, I run a realms server for my nieces, and I just can not stay on for more than 30 seconds. It is NOT my internet, it is NOT my computer. I removed the only thing it could be, which was an ASRock LAN accelerator, which is known for its stability. I dont get kicked anywhere else, so this has to be a bug on minecraft, and there should be a fix for it. However, the internet returns so much information that leads nowhere, that now, after 3 hours of searching, I am no closer to a solution than when I started.

Please help, I got two little girls who love this game, and I can not even text to them in game.

Oh, and before I go to bed, I also removed MC completely and reinstalled. I just cant find it.

Is it my wording? Should just go HALP I CAMP GET IT TO WURX, lol. No its a problem, and any suggestions would help.

Hello, here is the link:

http://paste.ubuntu.com/8275865/
I was not trying to be a smart ass, I was just making light in a bump. I have found this forum nothing but useful for years

I will try now, doing housework cause its sunday, sorry for the delays
aaaaaand it seems stable, unlike my realm
which is the conclusion I came to, its only the mc realm I have this problem on

gotta walk the dogs, gonna leave it on the server

So tool a walk 40 minutes ago, come back and still stable on the test server. So it is a realms problem, but yeah, there doesn't seem to be any clear way to report it.

yep, log in to my realm and boop, kicked in less than 20 seconds.

Less than 1mbps upload is pretty low... but then again, just playing on a server shouldn't demand a lot of upload bandwidth. I noticed it says you're in Sydney... perhaps you are just too physically far away from wherever the Minecraft realms server is located? Perhaps a traceroute is in order?

Already did a recreation, does anyone know where in mojang I can report this? We were cleared for realms in AU a few months ago or so, but this is just unbelievable. and yes, that is the upload speed on a generic DSL2 AU router, but hey, i got better ping than in Denver back in the day.

and how to traceroute to a realms server? I haven't done anything with realms yet other than order this one up.

enter the ip address of the server on a traceroute website, such as http://tools.pingdom.com/ping/

if you google traceroute, you'll find a bunch of sites that do it. take your pick.

realms is not a normal server, I have no ip that I know of. I know how to traceroute MY server, that is not the problem mate

you can also enter a host name... maybe try minecraft.net

i don't know anything about realms... do you get a site you go to to set it up or anything? or do you have to do everything from in game? if you do, you could try entering that host name...

Quote from sargos7»

you can also enter a host name... maybe try minecraft.net

i don't know anything about realms... do you get a site you go to to set it up or anything? or do you have to do everything from in game? if you do, you could try entering that host name...

Please stop guessing, I need proper information, not stabs in the dark.

Mods feel free to close this thread, I dont think I can get the help I need here, it is a Mojang problem at this stage.

Quote from Cunningstuffofstuff»

Please stop guessing, I need proper information, not stabs in the dark.

That's what troubleshooting is. Trial and error. No one, anywhere, ever, will be able to just tell you exactly what you need to do. You have to work with them to figure it out.