[b1060] and still no fix for "java.io.IOException: Bad packet id 81" wtf bukkit!

Discussion in 'Bukkit Discussion' started by Pixelzz, Aug 17, 2011.

Thread Status:
Not open for further replies.
  1. Offline

    Pixelzz

    Everyone has been talking about this error and still nobody knows the reason?
    >19:50:38 [SEVERE] java.io.IOException: Bad packet id 81
    >19:50:38 [SEVERE] at net.minecraft.server.Packet.a(Packet.java:73)
    >19:50:38 [SEVERE] at net.minecraft.server.NetworkManager.g(NetworkManager.java:149)
    >19:50:38 [SEVERE] at net.minecraft.server.NetworkManager.c(NetworkManager.java:259)
    >19:50:38 [SEVERE] at net.minecraft.server.NetworkReaderThread.run(SourceFile:84)
     
  2. Offline

    spunkiie

    please die asap
     
  3. Offline

    Orcem12

    Both of you, just stop. This is a waste of intelligence.
    @Pixelzz - you are the only one with error, so it's not bukkit.
     
  4. Offline

    Pixelzz

    no im not the only one look this error up on google theres many with this error
     
  5. Offline

    Orcem12

    Google? Your joking don't come to me with that. Update your Java.
     
  6. Offline

    Pixelzz

    yes google is a good way for checking if anyone else that uses bukkit gets this error. because it search for the phrase that i type in. Also im not running the server its hosted by "UpstreamGaming.com" Also im using build [#1060] an my only plugins are Vanilla, Worldedit, worldguard, spamhammer, and nocheat.
     
  7. Offline

    Orcem12

    Contact your host then. Don't blame Bukkit.
     
  8. Offline

    Pixelzz

    this error message spams my console as if someone was trying to log in because at the end of the error it always says a player lost connection.
    >20:19:33 [SEVERE] java.io.IOException: Bad packet id 81
    >20:19:33 [SEVERE] at net.minecraft.server.Packet.a(Packet.java:73)
    >20:19:33 [SEVERE] at net.minecraft.server.NetworkManager.g(NetworkManager.java:149)
    >20:19:33 [SEVERE] at net.minecraft.server.NetworkManager.c(NetworkManager.java:259)
    >20:19:33 [SEVERE] at net.minecraft.server.NetworkReaderThread.run(SourceFile:84)
    >20:19:33 [INFO] /64.79.109.130:57551 lost connection

    -Not the same ip everytime though
     
  9. Offline

    X8105

    same Error.
     
  10. Offline

    Jacek

    You get this error when people send stuff to the server that is not from a minecraft client, like trying to open the IP and port using a web browser for example.

    don't worry about it.
     
  11. Offline

    jeremytrains

    I get "Bad Packet Id: 71" when going to my server in mozilla
     
  12. Offline

    Jacek

    ;)
     
  13. Offline

    jeremytrains

    I just figured out my problem. I had hosting on a certain ip on port 25566. Some guy on port 9.... on the SAME IP (shared hosting) set up his minequery on 25566 and not 9..... for some reason. Contacted minestatus.net, removed him from the listing, now it is all fixed. If you look at the error, after the error, it says "-----ip----- lost connection". go to http://whatismyipaddress.com/ to then trace the ip. Type in the ------ip------ in the error into the little box next to "Additional Ip Details", and then click the button. This will trace back the ip to the thing that is accessing your server incorrectly. If you scroll down, copy the Hostname into your address bar and go to it. It might lead to minestatus.net. If it does, talk to the staff on IRC. I talked to them on IRC and they solved my problem. (I was not registered, but MineQuery was still querying me - so even if you aren't registered, that might be the problem.)

    Mod Edit (c0mp): Bolded and italicized last sentence, rather than shouting it with caps.
     
  14. Offline

    ViZiT

    sometimes it means that minecraft servertop sites where a u registred your server checking your server status

    it try to check users online if u don't have connector (don't remember the name) u have bad packet id 81. disable that option userscount. it helps Me =)
    sorry for my gorgeous english(try to write it in to russan =D)
     
Thread Status:
Not open for further replies.

Share This Page