fix: use fetchLatestWaWebVersion to prevent 405 connection failures#443
Merged
gavrielc merged 1 commit intoqwibitai:mainfrom Feb 24, 2026
Merged
Conversation
gavrielc
approved these changes
Feb 24, 2026
Collaborator
gavrielc
left a comment
gavrielc
left a comment
There was a problem hiding this comment.
Clutch fix. Gonna merge and then add a catch. Thanks!
Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
gavrielc
force-pushed
the
fix/wa-version-mismatch
branch
from
d4e4a47 to
b36fb5f
Compare
gavrielc
added a commit
that referenced
this pull request
Feb 24, 2026
The fetchLatestWaWebVersion call added in #443 could crash the connection flow if the HTTP fetch fails. Wrap with .catch() to log and fall back to the default Baileys version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Author
|
Sick! Happy I could help |
Peyton-Spencer
added a commit
to omniaura/omniclaw
that referenced
this pull request
Feb 24, 2026
- Port fetchLatestWaWebVersion fix from upstream qwibitai/nanoclaw#443 to prevent 405 "Method Not Allowed" errors when Baileys' hardcoded WA Web version falls behind WhatsApp's current protocol - Add exponential backoff to WhatsApp reconnect (3s → 6s → 12s … 5min cap) instead of retrying immediately, which was hammering WA servers and causing rate limiting that blocked re-authentication Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2 tasks
Peyton-Spencer
added a commit
to omniaura/omniclaw
that referenced
this pull request
Feb 24, 2026
- Port fetchLatestWaWebVersion fix from upstream qwibitai/nanoclaw#443 to prevent 405 "Method Not Allowed" errors when Baileys' hardcoded WA Web version falls behind WhatsApp's current protocol - Add exponential backoff to WhatsApp reconnect (3s → 6s → 12s … 5min cap) instead of retrying immediately, which was hammering WA servers and causing rate limiting that blocked re-authentication Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
vedtam
pushed a commit
to vedtam/nanoclaw
that referenced
this pull request
Feb 26, 2026
…wibitai#443) Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
TwinXu
pushed a commit
to TwinXu/nanoclaw
that referenced
this pull request
Feb 28, 2026
…wibitai#443) Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
TwinXu
pushed a commit
to TwinXu/nanoclaw
that referenced
this pull request
Feb 28, 2026
The fetchLatestWaWebVersion call added in qwibitai#443 could crash the connection flow if the HTTP fetch fails. Wrap with .catch() to log and fall back to the default Baileys version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
ManveerBhullar
pushed a commit
to ManveerBhullar/nanoclaw
that referenced
this pull request
Mar 1, 2026
…wibitai#443) Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
ManveerBhullar
pushed a commit
to ManveerBhullar/nanoclaw
that referenced
this pull request
Mar 1, 2026
The fetchLatestWaWebVersion call added in qwibitai#443 could crash the connection flow if the HTTP fetch fails. Wrap with .catch() to log and fall back to the default Baileys version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
index-engine
pushed a commit
to index-engine/nanoclaw
that referenced
this pull request
Mar 1, 2026
…wibitai#443) Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
index-engine
pushed a commit
to index-engine/nanoclaw
that referenced
this pull request
Mar 1, 2026
The fetchLatestWaWebVersion call added in qwibitai#443 could crash the connection flow if the HTTP fetch fails. Wrap with .catch() to log and fall back to the default Baileys version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
bagelagent
pushed a commit
to bagelagent/nanoclaw
that referenced
this pull request
Mar 3, 2026
…wibitai#443) Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
bagelagent
pushed a commit
to bagelagent/nanoclaw
that referenced
this pull request
Mar 3, 2026
The fetchLatestWaWebVersion call added in qwibitai#443 could crash the connection flow if the HTTP fetch fails. Wrap with .catch() to log and fall back to the default Baileys version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Mar 5, 2026
jenskock
pushed a commit
to jenskock/nanoclaw
that referenced
this pull request
Mar 6, 2026
…wibitai#443) Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
jenskock
pushed a commit
to jenskock/nanoclaw
that referenced
this pull request
Mar 6, 2026
The fetchLatestWaWebVersion call added in qwibitai#443 could crash the connection flow if the HTTP fetch fails. Wrap with .catch() to log and fall back to the default Baileys version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 task
bebekim
pushed a commit
to bebekim/goodclaw
that referenced
this pull request
Mar 14, 2026
…wibitai#443) Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
bebekim
pushed a commit
to bebekim/goodclaw
that referenced
this pull request
Mar 14, 2026
The fetchLatestWaWebVersion call added in qwibitai#443 could crash the connection flow if the HTTP fetch fails. Wrap with .catch() to log and fall back to the default Baileys version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
squarewings
pushed a commit
to squarewings/nanoclaw
that referenced
this pull request
Mar 15, 2026
…wibitai#443) Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
squarewings
pushed a commit
to squarewings/nanoclaw
that referenced
this pull request
Mar 15, 2026
The fetchLatestWaWebVersion call added in qwibitai#443 could crash the connection flow if the HTTP fetch fails. Wrap with .catch() to log and fall back to the default Baileys version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
onlyforart
referenced
this pull request
in onlyforart/nanoclaw
Mar 27, 2026
…443) Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
onlyforart
referenced
this pull request
in onlyforart/nanoclaw
Mar 27, 2026
The fetchLatestWaWebVersion call added in #443 could crash the connection flow if the HTTP fetch fails. Wrap with .catch() to log and fall back to the default Baileys version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
dm-j
pushed a commit
to dm-j/nanoclaw
that referenced
this pull request
Apr 13, 2026
…wibitai#443) Baileys' default WhatsApp version can fall behind when WhatsApp updates their protocol, causing 405 "Method Not Allowed" errors on the websocket handshake. This prevents both new authentication and reconnection. Now fetches the latest version on each connection so it stays current. Applied to both the runtime connection (whatsapp.ts) and the setup auth flow (whatsapp-auth.ts).
dm-j
pushed a commit
to dm-j/nanoclaw
that referenced
this pull request
Apr 13, 2026
The fetchLatestWaWebVersion call added in qwibitai#443 could crash the connection flow if the HTTP fetch fails. Wrap with .catch() to log and fall back to the default Baileys version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fetchLatestWaWebVersion()before creating the socket so it always uses a current versionFiles changed
src/channels/whatsapp.ts— runtime connectionsrc/whatsapp-auth.ts— setup auth flowTest plan
🤖 Generated with Claude Code