A Evolution API não cria códigos QR

[JBdesarrollo]

Welcome!

• Yes, I have searched for similar issues on GitHub and found none.

What did you do?

Ao criar uma instância da Evolution API para o Chatwoot usando a opção de criação automática, a inbox é criada no Chatwoot, mas o contato +123456 só envia a mensagem "init" e não gera o QR.
Também no /manager não são gerados QRs, aparece apenas o texto "Scan the QR code with your WhatsApp Web".

What did you expect?

Depois da mensagem "init" deveria chegar um código QR.

What did you observe instead of what you expected?

Não se observa nada de estranho além de que os QRs não são gerados, a inbox é criada normalmente.

Screenshots/Videos

No response

Which version of the API are you using?

2.2.3

What is your environment?

Linux

Other environment specifications

VPS de hostinger, sin docker, clonado de github.

If applicable, paste the log output

No response

Additional Notes

No response

[uzieljr]

Hi team,

I'm facing the same critical issue with Baileys (version 2.3000). My instance was working normally until the morning of May 27th, 2025. Suddenly, it stopped generating the QR Code and now it always gets stuck at the connecting state with no further progress.

I already:

• Deleted old sessions
• Cleared volumes and rebuilt the Docker container
• Restarted the app from scratch
• Tried from different browsers and environments

It seems like a WhatsApp Web protocol update broke compatibility with this version. Is there any confirmation or ongoing fix for this? Can you confirm if recent changes on the WhatsApp Web side triggered this behavior?

Thanks in advance!

Container logs:
[Evolution API] [XXXX-instance] v2.2.3 XXXX - Tue May 27 2025 23:39:52 INFO [ChannelStartupService] [string] Browser: Evolution API,Chrome,5.15.0-25-generic

[Evolution API] [XXXX-instance] v2.2.3 XXXX - Tue May 27 2025 23:39:52 INFO [ChannelStartupService] [string] Baileys version env: 2,3000,1015901307

{
local: 'p.sendData-Webhook-Global',
url: '',
event: 'connection.update',
instance: 'XXXX-instance',
{
instance: 'XXXX-instance',
state: 'connecting',
statusReason: 200
},
destination: '/connection-update',
date_time: '2025-05-27T23:40:25.020Z',
sender: undefined,
server_url: 'https://XXXX.com.br',
apikey: 'XXXX-XXXX-XXXX-XXXXXXXXXXXX'
}

[JBdesarrollo]

Hi team,

I'm facing the same critical issue with Baileys (version 2.3000). My instance was working normally until the morning of May 27th, 2025. Suddenly, it stopped generating the QR Code and now it always gets stuck at the connecting state with no further progress.

I already:

• Deleted old sessions
• Cleared volumes and rebuilt the Docker container
• Restarted the app from scratch
• Tried from different browsers and environments

It seems like a WhatsApp Web protocol update broke compatibility with this version. Is there any confirmation or ongoing fix for this? Can you confirm if recent changes on the WhatsApp Web side triggered this behavior?

Thanks in advance!

Container logs: [Evolution API] [XXXX-instance] v2.2.3 XXXX - Tue May 27 2025 23:39:52 INFO [ChannelStartupService] [string] Browser: Evolution API,Chrome,5.15.0-25-generic

[Evolution API] [XXXX-instance] v2.2.3 XXXX - Tue May 27 2025 23:39:52 INFO [ChannelStartupService] [string] Baileys version env: 2,3000,1015901307

{ local: 'p.sendData-Webhook-Global', url: '', event: 'connection.update', instance: 'XXXX-instance', { instance: 'XXXX-instance', state: 'connecting', statusReason: 200 }, destination: '/connection-update', date_time: '2025-05-27T23:40:25.020Z', sender: undefined, server_url: 'https://XXXX.com.br', apikey: 'XXXX-XXXX-XXXX-XXXXXXXXXXXX' }

Friend, if your problem is the same as mine, there is a solution. There was already an issue created a few hours ago that I didn’t see, and a lot of people have had this problem. The solution is to go to your .env file and change

CONFIG_SESSION_PHONE_VERSION=2.3000.1015901307

(that was the number I had) to

CONFIG_SESSION_PHONE_VERSION=2.3000.1023204200

Then restart your service, and that’s it.

[VitorS0uza]

mesma coisa qui

[mvmendes]

Same here. You probably need to upgrade Baileys in the package.json file:

    "baileys": "github:EvolutionAPI/Baileys",

[Webion2019]

I was having the same issue — I changed CONFIG_SESSION_PHONE_VERSÃO to 2.3000.1023204200, and this new version solved my problem. Thank you so much @JBdesarrollo !

[VitorS0uza]

I changed to 2.3000.1023204200 and solved my problem too.
but RAM and CPU consumption increased substantially. Here it went from 500mb to 900mb and 80% CPU usage, with 60 instances connected

[danilobreda]

solution in #1509
change CONFIG_SESSION_PHONE_VERSÃO

[mvmendes]

Thank you! CONFIG_SESSION_PHONE_VERSION=2.3000.1020885143 on .env solved!

[thexiox]

Does anyone know where to inform me about the version changes? because I went through the same thing, 1 hour trying different things until I changed the version and ready ....

[b8adel]

Thank you! CONFIG_SESSION_PHONE_VERSION=2.3000.1020885143 on .env solved! dont forget do save

[adriannoes]

Same here..

CONFIG_SESSION_PHONE_VERSION=2.3000.1020885143 on .env solved the problem..

thanks guys!

[yuri12344]

Same shit here, solved with 2.3000.1023204200

[darkklin]

can someone explain why it happened ?

p.s
it's happened because this guy updated the web version ? -> https://github.com/WhiskeySockets/Baileys/actions/runs/15287520324

[lucascopatti99]

Hi team,
I'm facing the same critical issue with Baileys (version 2.3000). My instance was working normally until the morning of May 27th, 2025. Suddenly, it stopped generating the QR Code and now it always gets stuck at the connecting state with no further progress.
I already:

• Deleted old sessions
• Cleared volumes and rebuilt the Docker container
• Restarted the app from scratch
• Tried from different browsers and environments

It seems like a WhatsApp Web protocol update broke compatibility with this version. Is there any confirmation or ongoing fix for this? Can you confirm if recent changes on the WhatsApp Web side triggered this behavior?
Thanks in advance!
Container logs: [Evolution API] [XXXX-instance] v2.2.3 XXXX - Tue May 27 2025 23:39:52 INFO [ChannelStartupService] [string] Browser: Evolution API,Chrome,5.15.0-25-generic
[Evolution API] [XXXX-instance] v2.2.3 XXXX - Tue May 27 2025 23:39:52 INFO [ChannelStartupService] [string] Baileys version env: 2,3000,1015901307
{ local: 'p.sendData-Webhook-Global', url: '', event: 'connection.update', instance: 'XXXX-instance', { instance: 'XXXX-instance', state: 'connecting', statusReason: 200 }, destination: '/connection-update', date_time: '2025-05-27T23:40:25.020Z', sender: undefined, server_url: 'https://XXXX.com.br', apikey: 'XXXX-XXXX-XXXX-XXXXXXXXXXXX' }

Friend, if your problem is the same as mine, there is a solution. There was already an issue created a few hours ago that I didn’t see, and a lot of people have had this problem. The solution is to go to your .env file and change

CONFIG_SESSION_PHONE_VERSION=2.3000.1015901307

(that was the number I had) to

CONFIG_SESSION_PHONE_VERSION=2.3000.1023204200

Then restart your service, and that’s it.

Thanks! Works for me too