Bad packet id 122. How can I fix this?

Discussion in 'Bukkit Help' started by Finkdaddy, Nov 8, 2012.

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

    Finkdaddy

    All of a sudden I can't connect to my server.
    It starts loading, but 2 seconds after starting I get kicked off with the following error:
    Internal exception: java.io.IOException: Bad packet id 122


    Does anyone know what this is and how to fix it?
    Thank you!

    ~Fred
     
  2. Offline

    Liam429

    Hi, i had this problem today and have had a similar problem but id 237. The only way I've found to fix this is to restart the server. This problem has only risen when the server was updated to 1.4 for me. I Hope this helps.
     
  3. Offline

    TnT

    Minecraft 1.4.4 seems to fix this issue. You will have to wait until it comes out for a true fix for this concern.
     
    Liam429 likes this.
  4. Offline

    Liam429

    Will this also fix the other problem i mentioned? (id 237) because i know about 5 people who have had the same experience as me with this issue and have only been able to rejoin the server after a restart. Is this the only known fix?
     
  5. Offline

    TnT

    1.4.4 seems to fix the "Bad Packet" issue, no matter the ID.
     
    Liam429 likes this.
  6. Offline

    md_5

    A bit of technical background info:
    The bad packet ID issue occurs when the server sends a packet that the client cannot translate. The bad packet id is simply the byte after the last good bit of data. Bad packet issues are very common when using proxies and server port systems, but in this case it is a Minecraft issue, fixed in 1.4.4
    The ID which is bad can be the same (indicating an issue in 1 block of code), or arbitrary indicating a dynamic section is wrong.
     
  7. Offline

    FrozenBrain

    For now, just block item frames with e.g. WorldGuard and remove all existing ones from your world.
    They're somehow causing this problem.
     
Thread Status:
Not open for further replies.

Share This Page