[SERVER] online-mode error 1.20.5-1.21.4

[notegorkaa]

• The FAQ doesn't contain a resolution to my issue

Versions

• minecraft-protocol: 1.51.0
• server: [email protected] (nmp server)
• node: 22.12.0

Detailed description of a problem

The nmp server does not connect the player if online-mode=true in versions 1.20.5-1.21.4 (766-769), kicking with the reason “Failed” or “Disconnected”.

Current code

const mcServer = require('flying-squid')

mcServer.createMCServer({
  motd: 'A Minecraft Server \nRunning flying-squid',
  port: 25565,
  'max-players': 10,
  'online-mode': true,
  logging: true,
  gameMode: 1,
  difficulty: 1,
  worldFolder: 'world',
  generation: {
    name: 'diamond_square',
    options: {
      worldHeight: 80
    }
  },
  kickTimeout: 10000,
  plugins: {

  },
  modpe: false,
  'view-distance': 10,
  'player-list-text': {
    header: 'Flying squid',
    footer: 'Test server'
  },
  'everybody-op': true,
  'max-entities': 100,
  version: '1.21.4'
})

Expected behavior

the player logs on to the server

Additional context

// 1.21.4 (769)
[10:58:15] [Render thread/INFO]: Connecting to 0.0.0.0, 25565


// 1.21.3 (768)
[10:54:54] [Render thread/INFO]: Connecting to 0.0.0.0, 25565
[10:54:55] [Netty Client IO #0/WARN]: ERROR IN Protocol1_21_2To1_21_4 IN REMAP OF LOGIN 0x00->0x00

// 1.21.1 (767)
[11:01:17] [Render thread/INFO]: Connecting to 0.0.0.0, 25565
[11:01:18] [Netty Client IO #0/WARN]: ERROR IN Protocol1_21To1_21_2 IN REMAP OF LOGIN 0x00->0x00

// 1.20.6 (766)
[11:03:29] [Render thread/INFO]: Connecting to 0.0.0.0, 25565
[11:03:30] [Netty Client IO #2/WARN]: ERROR IN Protocol1_21To1_21_2 IN REMAP OF LOGIN 0x00->0x00

// 1.20.4 (765)
no errors

[extremeheat]

You opened 2 issues.

#1370

[notegorkaa]

You opened 2 issues.

#1370

you misunderstand me, they're completely different mistakes. I used both flying-squid and nmp server, same errors. Specifically here the problem is with online-mode and that the server handles it wrong.

[notegorkaa]

reopen this

[TheRedXD]

Having the same exact issue on minecraft-protocol. This appears to be an actual bug, I'll look into it myself as well