Error in version 2025.2.1 -> Container being shut down #772

TitoBahe · 2025-02-04T13:44:42Z

TitoBahe
Feb 4, 2025

So, I got the last API image released a few days ago yesterday. It was working fine until now. The container was shut down, theres inumerous Error logs. I have no idea which is more important so I will be posting it all here.

 ERROR (NOWEBEngine/1): session:eQdlkmzpLsor2np1qYOE-clientId2 - unexpected error in 'processing message' {"session":"eQdlkmzpLsor2np1qYOE-clientId2"}
    err: {
      "type": "Error",
      "message": "Connection Closed",
      "stack":
          Error: Connection Closed
              at sendRawMessage (/app/node_modules/@adiwajshing/baileys/lib/Socket/socket.js:57:19)
              at sendNode (/app/node_modules/@adiwajshing/baileys/lib/Socket/socket.js:76:16)
              at sendReceipt (/app/node_modules/@adiwajshing/baileys/lib/Socket/messages-send.js:98:15)
              at /app/node_modules/@adiwajshing/baileys/lib/Socket/messages-recv.js:732:31
              at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
              at async /app/node_modules/@adiwajshing/baileys/lib/Utils/make-mutex.js:19:36
      "data": null,
      "isBoom": true,
      "isServer": false,
      "output": {
        "statusCode": 428,
        "payload": {
          "statusCode": 428,
          "error": "Precondition Required",
          "message": "Connection Closed"
        },
        "headers": {}
      }
    }

error: "Error: failed to find key \"AAAAAPTe\" to decode mutation\n at getKey (/app/node_modules/@adiwajshing/baileys/lib/Utils/chat-utils.js:192:19)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async decodeSyncdMutations (/app/node_modules/@adiwajshing/baileys/lib/Utils/chat-utils.js:161:21)\n at async decodeSyncdSnapshot (/app/node_modules/@adiwajshing/baileys/lib/Utils/chat-utils.js:274:37)\n at async /app/node_modules/@adiwajshing/baileys/lib/Socket/chats.js:382:70\n at async Object.transaction (/app/node_modules/@adiwajshing/baileys/lib/Utils/auth-utils.js:135:26)\n at async /app/node_modules/@adiwajshing/baileys/lib/Socket/chats.js:326:9\n at async /app/node_modules/@adiwajshing/baileys/lib/Utils/event-buffer.js:105:36\n at async processNotification (/app/node_modules/@adiwajshing/baileys/lib/Socket/messages-recv.js:374:21)\n at async /app/node_modules/@adiwajshing/baileys/lib/Socket/messages-recv.js:635:33\n at async /app/node_modules/@adiwajshing/baileys/lib/Utils/make-mutex.js:19:36\n at async Promise.all (index 0)\n at async handleNotification (/app/node_modules/@adiwajshing/baileys/lib/Socket/messages-recv.js:632:13)\n at async promise (/app/node_modules/@adiwajshing/baileys/lib/Socket/messages-recv.js:894:21)"

Does somebody know what happened?

ERROR (NOWEBEngine/1): session:eQdlkmzpLsor2np1qYOE-clientId4 - unexpected error in 'processing message' {"session":"eQdlkmzpLsor2np1qYOE-clientId4"}
    err: {
      "type": "TypeError",
      "message": "Cannot read properties of null (reading 'remoteJid')",
      "stack":
          TypeError: Cannot read properties of null (reading 'remoteJid')
              at stringifyMessageKey (/app/node_modules/@adiwajshing/baileys/lib/Utils/event-buffer.js:520:45)
              at append (/app/node_modules/@adiwajshing/baileys/lib/Utils/event-buffer.js:327:32)
              at Object.emit (/app/node_modules/@adiwajshing/baileys/lib/Utils/event-buffer.js:91:17)
              at processMessage (/app/node_modules/@adiwajshing/baileys/lib/Utils/process-message.js:218:20)
              at /app/node_modules/@adiwajshing/baileys/lib/Socket/chats.js:736:43
              at /app/node_modules/@adiwajshing/baileys/lib/Utils/event-buffer.js:105:42
              at /app/node_modules/@adiwajshing/baileys/lib/Socket/messages-recv.js:693:27
              at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
              at async /app/node_modules/@adiwajshing/baileys/lib/Utils/make-mutex.js:19:36
    }

ERROR (NOWEBEngine/1): session:h56TvmJ2viJUcOd9hAL8-clientId0 - failed to decrypt message {"session":"h56TvmJ2viJUcOd9hAL8-clientId0","key":{"remoteJid":"[email protected]","fromMe":false,"id":"3EB0204E23502AC2FA0068","participant":"5511999874984:[email protected]"}}
    err: {
      "type": "Error",
      "message": "No SenderKeyRecord found for decryption",
      "stack":
          Error: No SenderKeyRecord found for decryption
              at [email protected]::5511999874984::23 [as awaitable] (/app/node_modules/@adiwajshing/baileys/WASignalGroup/group_cipher.js:49:15)
              at async _asyncQueueExecutor (/app/node_modules/@adiwajshing/baileys/WASignalGroup/queue_job.js:20:29)
    }

Closing open session in favor of incoming prekey bundle
Closing session: SessionEntry {
  _chains: {
    'BbxhwltluFz3Nxi2HdgJT8EjS4QlF9JoLgj+rflPjVt3': { chainKey: [Object], chainType: 2, messageKeys: {} },
    'BXikg9xphjhKIYQtcKr+Th4orNknMhxOkToy4PDtmQsu': { chainKey: [Object], chainType: 2, messageKeys: {} },
    Bae48POFmylclhSAVDF8Lst9wHCLbGdwd1ZxBgyYIuEu: { chainKey: [Object], chainType: 1, messageKeys: {} }
  },
  registrationId: 211,
  currentRatchet: {
    ephemeralKeyPair: {
      pubKey: <Buffer 05 a7 b8 f0 f3 85 9b 29 5c 96 14 80 54 31 7c 2e cb 7d c0 70 8b 6c 67 70 77 56 71 06 0c 98 22 e1 2e>,
      privKey: <Buffer 98 93 9c f5 51 22 24 10 5d de 59 8a 89 c4 79 b7 84 95 c8 89 39 9f 48 44 c2 87 d1 a5 8d d8 9a 7d>
    },
    lastRemoteEphemeralKey: <Buffer 05 78 a4 83 dc 69 86 38 4a 21 84 2d 70 aa fe 4e 1e 28 ac d9 27 32 1c 4e 91 3a 32 e0 f0 ed 99 0b 2e>,
    previousCounter: 3,
    rootKey: <Buffer 24 fd 76 19 15 d3 a1 2f 2a 3d a6 c9 aa 8a 55 32 df d6 17 80 75 e5 aa d0 f5 b3 58 7c 81 9f 54 83>
  },
  indexInfo: {
    baseKey: <Buffer 05 0b 8a 6f ed 3c 71 32 81 d5 a5 51 e4 48 24 fc 32 67 8e 6a 14 3f 64 f7 63 f0 35 eb 6f 1c b3 b4 08>,
    baseKeyType: 1,
    closed: -1,
    used: 1738365278069,
    created: 1738247438096,
    remoteIdentityKey: <Buffer 05 ca 6f ed b2 4b 5c 64 58 b7 9c 8d ae 87 c5 f5 77 9d 5b 9b 0d 9e da ea fb 33 e4 04 50 44 63 55 05>
  }
}

ERROR (NOWEBEngine/1): session:xqBFeOe8aUuZI8tfnSDv-clientId0 - unexpected error in 'processing message' {"session":"xqBFeOe8aUuZI8tfnSDv-clientId0"}
    err: {
      "type": "TypeError",
      "message": "Cannot read properties of null (reading 'remoteJid')",
      "stack":
          TypeError: Cannot read properties of null (reading 'remoteJid')
              at stringifyMessageKey (/app/node_modules/@adiwajshing/baileys/lib/Utils/event-buffer.js:520:45)
              at append (/app/node_modules/@adiwajshing/baileys/lib/Utils/event-buffer.js:327:32)
              at Object.emit (/app/node_modules/@adiwajshing/baileys/lib/Utils/event-buffer.js:91:17)
              at processMessage (/app/node_modules/@adiwajshing/baileys/lib/Utils/process-message.js:218:20)
              at /app/node_modules/@adiwajshing/baileys/lib/Socket/chats.js:736:43
              at /app/node_modules/@adiwajshing/baileys/lib/Utils/event-buffer.js:105:42
              at /app/node_modules/@adiwajshing/baileys/lib/Socket/messages-recv.js:693:27
              at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
              at async /app/node_modules/@adiwajshing/baileys/lib/Utils/make-mutex.js:19:36
    }

Closing stale open session for new outgoing prekey bundle
Closing session: SessionEntry {
  _chains: {
    'BThSo9kLj2oBmK8uI3Nj8KNKeP1bXgDGlHgiP+9QJW4U': { chainKey: [Object], chainType: 1, messageKeys: {} }
  },
  registrationId: 10284,
  currentRatchet: {
    ephemeralKeyPair: {
      pubKey: <Buffer 05 38 52 a3 d9 0b 8f 6a 01 98 af 2e 23 73 63 f0 a3 4a 78 fd 5b 5e 00 c6 94 78 22 3f ef 50 25 6e 14>,
      privKey: <Buffer 30 cd 58 75 5c 01 d5 cb ad 68 99 39 85 6a cd 2e 81 10 ec d8 4e d4 37 d1 4c 11 92 51 14 0d cd 76>
    },
    lastRemoteEphemeralKey: <Buffer 05 30 fc 71 7d 79 78 92 1d ef a2 34 d6 1f b5 56 17 cc b3 6a 4a a7 62 84 0d ad 16 e2 8b 3a 0b d3 4c>,
    previousCounter: 0,
    rootKey: <Buffer 52 69 95 48 84 78 3e bb b7 13 fc cb 13 24 60 cf 8c 87 b6 93 7e 06 de 38 c5 de 1b cd 68 d1 87 4c>
  },
  indexInfo: {
    baseKey: <Buffer 05 75 7f 6e 98 14 84 09 0a ae 56 0b 67 78 40 48 88 18 ca 44 4f b6 ce ea d0 c2 5e b5 4f 15 83 db 74>,
    baseKeyType: 1,
    closed: -1,
    used: 1737205251705,
    created: 1737205251705,
    remoteIdentityKey: <Buffer 05 01 77 7f cc c3 97 ef 0e 94 a2 b2 2c 0d dd 29 9b 01 ca b0 70 66 28 29 2f 30 94 4e e5 94 ce 47 1a>
  },
  pendingPreKey: {
    signedKeyId: 1,
    baseKey: <Buffer 05 75 7f 6e 98 14 84 09 0a ae 56 0b 67 78 40 48 88 18 ca 44 4f b6 ce ea d0 c2 5e b5 4f 15 83 db 74>,
    preKeyId: 385
  }
}
Failed to decrypt message with any known session...
Session error:Error: Bad MAC Error: Bad MAC
    at Object.verifyMAC (/app/node_modules/libsignal/src/crypto.js:87:15)
    at SessionCipher.doDecryptWhisperMessage (/app/node_modules/libsignal/src/session_cipher.js:251:16)
    at async SessionCipher.decryptWithSessions (/app/node_modules/libsignal/src/session_cipher.js:147:29)
    at async 552140402122.0 [as awaitable] (/app/node_modules/libsignal/src/session_cipher.js:171:28)
    at async _asyncQueueExecutor (/app/node_modules/libsignal/src/queue_job.js:20:29)

[13:30:10.524] ERROR (WhatsappSession/1): session:eQdlkmzpLsor2np1qYOE-clientId0 - Connection closed due to 'Error: Connection Failure', do not reconnect the session. {"session":"eQdlkmzpLsor2np1qYOE-clientId0"}

Answered by devlikepro

Feb 6, 2025

it happend after one number got blocked by whatsapp

Do you mean like one got blocked, but other got the error messages?
Interesting.

Does that GOWS have a fallback logic in that case?

GOWS just more stable in many cases.

Where Can I find the source code, Pro tier members have access, right?

Correct, PRO level required for this (I see you have one :):

WAHA Plus: https://github.com/devlikeapro/waha-plus
Dashboard: https://github.com/devlikeapro/waha-hub
GOWS source code: https://github.com/devlikeapro/gows-plus

View full answer

devlikepro · 2025-02-05T12:07:58Z

devlikepro
Feb 5, 2025
Maintainer

Hi! What database do you use? Looks like it missed few keys, try repairing your session (logout/scan qr code again)

Try switching to GOWS engine (you'll have to create new sessions and scan QR codes tho), it has almost all features as NOWEB, but it's much stable with such errors.

4 replies

devlikepro Feb 5, 2025
Maintainer

https://waha.devlike.pro/docs/how-to/engines/#gows

TitoBahe Feb 5, 2025
Author

So, I am using mongoDB, the problem is that it happend after one number got blocked by whatsapp. I am afraid it will happen evrytime a number gets blocked there

TitoBahe Feb 5, 2025
Author

Does that GOWS have a fallback logic in that case?
Where Can I find the source code, Pro tier members have access, right? I can create a fall back logic for that.

devlikepro Feb 6, 2025
Maintainer

it happend after one number got blocked by whatsapp

Do you mean like one got blocked, but other got the error messages?
Interesting.

Does that GOWS have a fallback logic in that case?

GOWS just more stable in many cases.

Where Can I find the source code, Pro tier members have access, right?

Correct, PRO level required for this (I see you have one :):

WAHA Plus: https://github.com/devlikeapro/waha-plus
Dashboard: https://github.com/devlikeapro/waha-hub
GOWS source code: https://github.com/devlikeapro/gows-plus

Answer selected by TitoBahe

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error in version 2025.2.1 -> Container being shut down #772

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 1 comment 4 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Error in version 2025.2.1 -> Container being shut down #772

TitoBahe Feb 4, 2025

Replies: 1 comment · 4 replies

devlikepro Feb 5, 2025 Maintainer

devlikepro Feb 5, 2025 Maintainer

TitoBahe Feb 5, 2025 Author

TitoBahe Feb 5, 2025 Author

devlikepro Feb 6, 2025 Maintainer

TitoBahe
Feb 4, 2025

Replies: 1 comment 4 replies

devlikepro
Feb 5, 2025
Maintainer

devlikepro Feb 5, 2025
Maintainer

TitoBahe Feb 5, 2025
Author

TitoBahe Feb 5, 2025
Author

devlikepro Feb 6, 2025
Maintainer