[BUG] 405 Method Not Allowed error

[DevelopmentsEASOFT]

Hello, I’m experiencing an issue when trying to start a new WhatsApp session using Baileys. The connection fails immediately with a 405 Method Not Allowed error and the WebSocket cannot connect to WhatsApp.

{
"error": {
"data": {
"reason": "405",
"location": "lla"
},
"isBoom": true,
"isServer": false,
"output": {
"statusCode": 405,
"payload": {
"statusCode": 405,
"error": "Method Not Allowed",
"message": "Connection Failure"
},
"headers": {}
}
},
"date": "2025-10-15T14:33:13.295Z"
}

Steps to reproduce:

Start a new session with useMultiFileAuthState.

Wait for the QR code or connection update.

Instead of receiving a QR, the connection closes with the error above.

Expected behavior: A QR code should be generated so the user can scan and log in.

Actual behavior: The socket fails to connect and throws 405 Method Not Allowed – Connection Failure.

Environment:

Baileys version: LATEST

Node.js version: LATEST

OS: Windows

[ddanjos]

Please, read the documentation: https://baileys.wiki/docs/socket/connecting

[medeirosnvk]

Same problem here! Everything was working normally and then this problem suddenly started without changing anything. I've already updated a library, packages, connections, and nothing.

Can anyone help?

[hugoafj]

same issue.

[amratef503092]

same issue

[jpinedacastell]

same issue too.

[sinticbolivia]

yep, same issue here

[joaovitorssouza]

Same issue.

[jpinedacastell]

npm install @whiskeysockets/baileys@6.6.0
use this version and now is working.

[viniciussricci]

It looks like this issue may be related to the WhatsApp version mismatch that has been discussed in other threads.

Baileys recommends using the default version when creating the socket, but after some recent WhatsApp updates, errors with QR code generation and unexpected disconnections started appearing.

Until the default version is updated in the stable Baileys release, a temporary workaround is to set the version statically:

const WHATSAPP_VERSION: [number, number, number] = [2, 3000, 1027934701];

const sock = makeWASocket({
  version: WHATSAPP_VERSION,
  auth: ...
});

This behavior seems to reflect the same underlying issue already mentioned in other version-related discussions, so aligning the version manually should help mitigate it until Baileys’ internal default catches up.

[rmichelena]

I can confirm that the above solution (hardcoded WhatsApp version) does work !
thanks!

[rmichelena]

And maybe it has to be with the fact that I'm using "Windows" as the WhatsApp client identification... because another client which identifies itself as Ubuntu has not (yet) suffered this problem.

[medeirosnvk]

Parece que esse problema pode estar relacionado à incompatibilidade de versões do WhatsApp que foi discutida em outros tópicos.

Baileys recomenda usar a versão padrão ao criar o soquete, mas depois de algumas atualizações recentes do WhatsApp, erros com a geração de código QR e desconexões inesperadas começaram a aparecer.

Até que a versão padrão seja atualizada na versão estável do Baileys, uma solução temporária é definir a versão estaticamente:

const WHATSAPP_VERSION: [number, number, number] = [2, 3000, 1027934701];

const sock = makeWASocket({
version: WHATSAPP_VERSION,
auth: ...
});
Esse comportamento parece refletir o mesmo problema subjacente já mencionado em outras discussões relacionadas à versão, portanto, alinhar a versão manualmente deve ajudar a mitigá-lo até que o padrão interno do Baileys o alcance.

Thanks friend! Updating to the latest stable version and downgrading this version worked!

[ssantss]

It looks like this issue may be related to the WhatsApp version mismatch that has been discussed in other threads.

Baileys recommends using the default version when creating the socket, but after some recent WhatsApp updates, errors with QR code generation and unexpected disconnections started appearing.

Until the default version is updated in the stable Baileys release, a temporary workaround is to set the version statically:

const WHATSAPP_VERSION: [number, number, number] = [2, 3000, 1027934701];

const sock = makeWASocket({
version: WHATSAPP_VERSION,
auth: ...
});
This behavior seems to reflect the same underlying issue already mentioned in other version-related discussions, so aligning the version manually should help mitigate it until Baileys’ internal default catches up.

Amigo muchas gracias! funciono perfecto!