Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[Bug / WhatsApp Ban]: Session disconnected with 401 device_removed and 24h restriction on Baileys engine

Offen
  • Stimmt etwas nicht?
#2,693 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
api, backend

Rechercherichtung

Start by examining the WHATSAPP-BAILEYS connection handling in v2.3.7 and the /instance/fetchInstances response for 401 device_removed; the issue names no source file or test. Reproduce or correlate the disconnect with the reported WhatsApp restriction using the available connection and Docker logs, and define done as an identified, actionable cause or a documented limitation with supporting evidence.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug
Welcome!
  • Yes, I have searched for similar issues on GitHub and found none.
What did you do?

We configured an instance (taha_store) using the WHATSAPP-BAILEYS integration in Evolution API v2.3.7 running on a cloud VPS.

The instance was handling strictly reactive, inbound customer service requests (price queries and warranty questions). We implemented human typing presence simulation (sendPresence: composing with a 2-second delay) and anti-spam debouncing (2.5s window). No bulk/mass messages or broadcasts were ever sent.

What did you expect?

We expected the multi-device connection to remain stable and connected continuously for legitimate inbound customer service conversations.

What did you observe instead of what you expected?

The instance suddenly disconnected with error code 401 (conflict: device_removed).

On the physical phone, WhatsApp logged out of the linked devices session and displayed a 24-hour temporary restriction stating that an unofficial application was detected.

Error payload from /instance/fetchInstances:

{
  "instance": "tastore",
  "connectionStatus": "close",
  "integration": "WHATSAPP-BAILEYS",
  "disconnectionReasonCode": 401,
  "disconnectionObject": {
    "error": {
      "data": {
        "tag": "conflict",
        "attrs": {
          "type": "device_removed"
        }
      },
      "isBoom": true,
      "isServer": false,
      "output": {
        "statusCode": 401,
        "error": "Unauthorized",
        "message": "Stream Errored (conflict)"
      }
    }
  }
}

### Screenshots/Videos

_No response_

### Which version of the API are you using?

v2.3.7


### What is your environment?

Windows

### Other environment specifications

Docker

- OS: Ubuntu 22.04 LTS (Cloud VPS)
- Node.js version: v20+ / Docker latest
- Integration: WHATSAPP-BAILEYS
- Country / Region: Libya (+218)

### If applicable, paste the log output

_No response_

### Additional Notes

_No response_
Vorherrschende Sprache
TypeScript
Sterne
9.7k
Forks
7.3k
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus evolution-foundation/evolution-api

Alle Issues in evolution-foundation/evolution-api

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.