Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Error 405 - Connection Failure #999

Open
jocimarlopes opened this issue Aug 23, 2024 · 17 comments
Open

[BUG] Error 405 - Connection Failure #999

jocimarlopes opened this issue Aug 23, 2024 · 17 comments
Labels
bug Something isn't working

Comments

@jocimarlopes
Copy link

Describe the bug
I has this error today, I tryed to update to 6.7.7, but even with that it doesn't start, it just stays with this error.

To Reproduce
Steps to reproduce the behavior:

  1. npm i
  2. node app.js (run an project with WhiskeySockets/Baileys)
  3. The QR Code doesn't even appear, it simply gives error 405.
@jocimarlopes jocimarlopes added the bug Something isn't working label Aug 23, 2024
@rasyidrafi
Copy link

Encountered the same issue; I think WhatsApp updated their WebSocket protocol, which makes the library unable to connect to WhatsApp.

@clifthanger
Copy link

i have same issue, but solved with update the latest update

@jocimarlopes
Copy link
Author

I verify the Web Socket Protocol WSS, its the same at all.
I think I'm doing any thing to broke the latest update.

I'll debug that and If works, I post here.

@sairmali
Copy link

+1

@rafaelpoa
Copy link

"I'm facing the same problem since yesterday. I've tested in every possible way, but it keeps returning a 405 error.

@rafaelpoa
Copy link

I was facing the same connection issue with a 405 error. I tested with version 6.7.6 and 6.7.7, both with the same problem. I followed a friend's advice and downgraded to 6.6.0. Now it works perfectly.

@rasyidrafi
Copy link

rasyidrafi commented Aug 23, 2024

try do npm update @whiskeysockets/baileys
it solve for me

@rcesar
Copy link

rcesar commented Aug 23, 2024

I have a same issue using version 6.7.5

@shuxter
Copy link

shuxter commented Aug 23, 2024

I have a same issue using version 6.7.5

The maintainers recommend updating to 6.7.7 and either using the default version which is 2.3000.1015901307
and do not use the fetchLatestBaileysVersion as it will bring a version that will break your code. We updated to 6.7.7 and use the default version and the errors have not come back.

@jocimarlopes
Copy link
Author

Someone, I tried to update to version 6.7.7, I tried to downgrade to version 6.6.0.

But all methods lead to the same error (405).

If anyone has an alternative, let me know. I will contact my internet provider to check if there was any blocking, but it would be too much of a coincidence for it to happen on the same day that there was a bug for more than one person.

If anyone has a solution, please post it here.
The version I was using is 6.7.5

Here my dependencies:

"dependencies": {
"@hapi/boom": "^10.0.1",
"@seald-io/nedb": "^4.0.4",
"@whiskeysockets/baileys": "^6.7.5",
"amqplib": "^0.10.4",
"axios": "^1.7.2",
"chalk": "^4.1.0",
"dotenv": "^8.2.0",
"form-data": "^4.0.0",
"format-duration-time": "^1.5.4",
"fs-extra": "^9.0.1",
"hercai": "^12.3.2",
"jimp": "^0.16.1",
"link-preview-js": "^3.0.5",
"lowdb": "^7.0.1",
"moment-timezone": "^0.5.31",
"node-cache": "^5.1.2",
"p-queue": "^8.0.1",
"pino": "^8.19.0",
"pretty-num": "^0.5.0",
"prompt": "^1.1.0",
"qrcode": "^1.5.4",
"qrcode-terminal": "^0.12.0",
"socket.io-client": "^4.7.5"
},

Thanks!

@andreocunha
Copy link

version 6.7.7 is working fine for me. I no longer receive the 405 error.

@Lewson
Copy link

Lewson commented Aug 23, 2024

Fixei em 6.6.0. Funcionou pra mim.
Era assim:
"@whiskeysockets/baileys": "^6.6.0",

Deixei assim:
"@whiskeysockets/baileys": "6.6.0",

Depois:
pnpm i

Funcionou!!

@jocimarlopes
Copy link
Author

jocimarlopes commented Aug 23, 2024

Fixei em 6.6.0. Funcionou pra mim. Era assim: "@whiskeysockets/baileys": "^6.6.0",

Deixei assim: "@whiskeysockets/baileys": "6.6.0",

Depois: pnpm i

Funcionou!!

You are the man! Worket for me! Thank you so much.
Só agora notei que tu é brasileiro também! Valeu cara, funcionou aqui.
E realmente, ontem eu tinha dado um npm update, depois disso até rodou um tempo, mas começou a crashar.

@rafaelpoa
Copy link

I have a same issue using version 6.7.5

The maintainers recommend updating to 6.7.7 and either using the default version which is 2.3000.1015901307 and do not use the fetchLatestBaileysVersion as it will bring a version that will break your code. We updated to 6.7.7 and use the default version and the errors have not come back.

it actually worked. Latest version of baileys and using the recommended version.

image

@jocimarlopes
Copy link
Author

Eu estava usando a versão que vem no fetchLatestWaWebVersion()

image

Consegui resolver aqui, obrigado.

@TheArKaID
Copy link

TheArKaID commented Sep 17, 2024

The maintainers recommend updating to 6.7.7 and either using the default version which is 2.3000.1015901307 and do not use the fetchLatestBaileysVersion as it will bring a version that will break your code. We updated to 6.7.7 and use the default version and the errors have not come back.

My running app broken since last month, updating to 6.7.7 didn't literally help me out. Just found that I use fetchLatestWaWebVersion() for makeWASocket(), now I just set it to fetchLatestBaileysVersion() so it could adjust with WhiskeySockets/Baileys

@ranggaAdiPratama
Copy link

here's what I found

`
const {
default: makeWASocket,
useMultiFileAuthState,
fetchLatestBaileysVersion,
DisconnectReason
} = require("@whiskeysockets/baileys");

const { state, saveCreds } = await useMultiFileAuthState("auth_info");
const { version } = await fetchLatestBaileysVersion();

const sock = makeWASocket({
auth: state,
version
});
`

it works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

12 participants