Bad packet id 254

Discussion in 'Bukkit Help' started by THG3, Sep 14, 2011.

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

    THG3

    Code:
    14.09 17:11:57 [Server] SEVERE     at net.minecraft.server.NetworkReaderThread.run(SourceFile:84)
    14.09 17:11:57 [Server] SEVERE     at net.minecraft.server.NetworkManager.c(NetworkManager.java:259)
    14.09 17:11:57 [Server] SEVERE     at net.minecraft.server.NetworkManager.g(NetworkManager.java:149)
    14.09 17:11:57 [Server] SEVERE     at net.minecraft.server.Packet.a(Packet.java:73)
    14.09 17:11:57 [Server] SEVERE java.io.IOException: Bad packet id 254
    Does anyone know what's causing this? I am having a hard time finding literature on it..
     
  2. Offline

    1lann

    Are you possibly using items on the server that don't exist in normal minecraft?
     
  3. Offline

    strontkever

    i get the same

    i think its people trying to connect with 1.8 while im 1.7, sicne theres no messages about outdated server
     
  4. Offline

    kakashi

    yes i tested this, you get this message when some1 tries to refresh or connect to the server using a 1.8 client
     
  5. Offline

    andrewkm

    This is due to users connecting to your server with the 1.8 client. I am seeing it all over my console.
     
  6. Offline

    shatteredbeam

    You can safely ignore this, the above people are correct - its just the 1.8 client trying to connect to an older version. We've been seeing it regularly since 1.8 was leaked.
     
  7. Offline

    LEOcab

    I always knew what this was, but how come I still get "Outdated server!" messages every now and then? Does it have something to do with the auth servers outage earlier?
     
  8. Offline

    strontkever

    i tried connecting to my server with 1.8: packet error
    then i tried again: outdated server
     
  9. Offline

    shatteredbeam

    No sir. Outdated server simply is coming up because 1.8 has been released today, and there is no 1.8 for Bukkit thus far. Your server IS outdated, but that will go away once you update. (when you can)

    If you updated your client to 1.8, you will not be able to join a 1.7 server.
     
  10. Offline

    Speedy64

    i got this error anytime on bukkit#1060 server now with OLD client also! Any player here even not updated cant connect to the server - as soon as we switch to offline mode all is fine but we dont want that - so what can we do to let players connect?
    another test-server with 1.8 and then new client on same root is running fine - but all 1.7.3 are "bad login" - and yes i tried with 1.7.3-client. help
     
  11. Offline

    THG3

    Thanks guys, appreciate the info. I keep getting bad login though when I try to connect to my 1.7 server with a 1.7 client.
     
  12. Offline

    stkeroro

    same here, maybe spout?
     
  13. Offline

    THG3

    Y
    Yeah same... hrm
     
  14. Offline

    stkeroro

    clean craftbukkit install= bad packet id, tested
     
  15. Offline

    The_Shrike

    CB 1060, No Spout, MC 1.7.3, and haven't updated the server OR the client. Getting "Bad Login".
    We don't want to update until we've got Bukkit & plugin support, so I'm guessing we're SOL?
     
  16. Offline

    Lolmewn

    Actually, ur screwed.
     
    Grotznak likes this.
  17. Offline

    Speedy64

    also other servers had that problem - notch-bug?
    but now all is fine again - would say minecraft.net-login was failed in some case

    ps: no spout
     
  18. Offline

    The_Shrike

    Thanks for the helpful reply!

    Anyway, looks like it was a MC issue that was resolved by Mojang.
     
  19. Offline

    Lolmewn

    I know I'm helpful =D
     
  20. Offline

    Sahee

    When i get this error 100x my serwer go off -.-
    Code:
    04:32:19 [SEVERE] java.io.IOException: Bad packet id 254
    04:32:25 [SEVERE]       at net.minecraft.server.Packet.a(Packet.java:73)
    04:32:26 [SEVERE]       at net.minecraft.server.NetworkManager.g(NetworkManager.java:149)
    04:32:35 [SEVERE]       at net.minecraft.server.NetworkManager.c(NetworkManager.java:259)
    04:32:41 [SEVERE]       at net.minecraft.server.NetworkReaderThread.run(SourceFile:84)
    
     
  21. Offline

    chausser

    The bad packet id 254 comes from the new multiplayer server status screen. When a user opens that page it "pings" your server with that packet to see if it is online or not and to get other various data about it. If you are still running a 1.7.* server it wont know how to handle that packet and throw an error. As far as i can tell its not really server impacting... It may be if you run a large server and a lot of people have you on their multiplayer selection screens, you may see an increase in traffic from it.

    Just my thoughts on the matter.
     
  22. Offline

    recondelta090

    my server says bad packet id 254 when it tries to start and is stuck trying to start
     
  23. Offline

    ledodreadlow

    This is true! The "outdated server" message you might get is someone actually connecting to your server that has been saved to that list. So that's why the random message may appear sometimes. The rest of the time is strictly a "ping" error.
     
  24. Offline

    PatrickFreed

    I've been having worse issues with this. It gets to the point where it pings so often the server won't allow anyone to log in.
     
Thread Status:
Not open for further replies.

Share This Page