We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I attempt to execute npm run server localhost 8123 1XXXXXXXXXX, I receive the following:
npm run server localhost 8123 1XXXXXXXXXX
> [email protected] server > node src/server.js localhost 8123 1XXXXXXXXXX [20:09:46.801] INFO (2300): connection update {"connection":"connecting","receivedPendingNotifications":false} [20:09:51.414] INFO (2300): connection update {"connection":"close","lastDisconnect":{"error":{"data":{"reason":"405","location":"odn"},"isBoom":true,"isServer":false,"output":{"statusCode":405,"payload":{"statusCode":405,"error":"Method Not Allowed","message":"Connection Failure"},"headers":{}}},"date":"2023-10-10T20:09:51.400Z"}}
The phone number is registered with WhatsApp, and I can send messages to it via a different WhatsApp address.
I expected to see a QR code during the first run. Did I do something wrong? Any other thoughts about how to debug the issue?
The text was updated successfully, but these errors were encountered:
Same here: Maybe it has something to to with this bug? WhiskeySockets/Baileys#353
# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # npm -v 10.2.4 # node -v v20.11.1
Sorry, something went wrong.
No branches or pull requests
When I attempt to execute
npm run server localhost 8123 1XXXXXXXXXX
, I receive the following:The phone number is registered with WhatsApp, and I can send messages to it via a different WhatsApp address.
I expected to see a QR code during the first run. Did I do something wrong? Any other thoughts about how to debug the issue?
The text was updated successfully, but these errors were encountered: