Skip to content

A Evolution API não cria códigos QR #1511

Closed
Closed
A Evolution API não cria códigos QR#1511
Labels
bugSomething isn't working

Description

@JBdesarrollo
JBdesarrollo
opened on May 28, 2025

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

Activity

  1. JBdesarrollo
    added
    bugSomething isn't working
    on May 28, 2025

  2. uzieljr commented on May 28, 2025

    @uzieljr
    uzieljr
    on May 28, 2025

    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'
    }

  3. JBdesarrollo commented on May 28, 2025

    @JBdesarrollo
    JBdesarrollo
    on May 28, 2025
    Author

    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.

  4. VitorS0uza commented on May 28, 2025

    @VitorS0uza
    VitorS0uza
    on May 28, 2025

    mesma coisa qui

  5. mvmendes commented on May 28, 2025

    @mvmendes
    mvmendes
    on May 28, 2025

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

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

  6. Webion2019 commented on May 28, 2025

    @Webion2019
    Webion2019
    on May 28, 2025

    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 !

  7. VitorS0uza commented on May 28, 2025

    @VitorS0uza
    VitorS0uza
    on May 28, 2025

    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

  8. danilobreda commented on May 28, 2025

    @danilobreda
    danilobreda
    on May 28, 2025

    solution in #1509
    change CONFIG_SESSION_PHONE_VERSÃO

  9. mvmendes commented on May 28, 2025

    @mvmendes
    mvmendes
    on May 28, 2025

    Thank you! CONFIG_SESSION_PHONE_VERSION=2.3000.1020885143 on .env solved!

  10. thexiox commented on May 28, 2025

    @thexiox
    thexiox
    on May 28, 2025

    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 ....

  11. b8adel commented on May 28, 2025

    @b8adel
    b8adel
    on May 28, 2025

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

  12. adriannoes commented on May 28, 2025

    @adriannoes
    adriannoes
    on May 28, 2025

    Same here..

    CONFIG_SESSION_PHONE_VERSION=2.3000.1020885143 on .env solved the problem..

    thanks guys!

  13. yuri12344 commented on May 28, 2025

    @yuri12344
    yuri12344
    on May 28, 2025

    Same shit here, solved with 2.3000.1023204200

  14. darkklin commented on May 28, 2025

    @darkklin
    darkklin
    on May 28, 2025

    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

  15. lucascopatti99 commented on May 28, 2025

    @lucascopatti99
    lucascopatti99
    on May 28, 2025

    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

  16. 48 remaining items

  17. netdados commented on Jul 16, 2025

    @netdados
    netdados
    on Jul 16, 2025 via email

  18. samchambela commented on Aug 21, 2025

    @samchambela
    samchambela
    on Aug 21, 2025

    CONFIG_SESSION_PHONE_VERSION=2.3000.1023204200

    You're a life saver

  19. brunodsstudio commented on Aug 29, 2025

    @brunodsstudio
    brunodsstudio
    on Aug 29, 2025

    CONFIG_SESSION_PHONE_VERSION = 2.3000.1024363850

    COMO UMA LUVA!

  20. isaquetdiniz commented on Sep 3, 2025

    @isaquetdiniz
    isaquetdiniz
    on Sep 3, 2025

    CONFIG_SESSION_PHONE_VERSION=2.3000.1023204200

    It worked!

  21. DavidsonGomes
    closed this as completedon Sep 9, 2025

  22. AlejandroCaruso21 commented on Oct 14, 2025

    @AlejandroCaruso21
    AlejandroCaruso21
    on Oct 14, 2025

    Estoy teniendo problemas de conectar, el QR no esta figurando.
    tengo la versión CONFIG_SESSION_PHONE_VERSION=2.3000.1023204200
    pero no me deja.
    segun esta web: https://wppconnect.io/whatsapp-versions/#:~:text=Current%20Version,%2C%2010:23:57%20PM
    seria esta 2.3000.1028395461-alpha
    pero no me esta dejando, alguien sabe?

  23. thunnior commented on Oct 14, 2025

    @thunnior
    thunnior
    on Oct 14, 2025

    New Version worked for me:
    CONFIG_SESSION_PHONE_VERSION=2.3000.1028401180

  24. Danilobrm commented on Oct 15, 2025

    @Danilobrm
    Danilobrm
    on Oct 15, 2025

    New Version worked for me: CONFIG_SESSION_PHONE_VERSION=2.3000.1028401180

    worked for me as well

    before I was using: CONFIG_SESSION_PHONE_VERSION=2.3000.1023204200
    and it was working, but then stopped

    now: CONFIG_SESSION_PHONE_VERSION=2.3000.1028401180
    works

  25. cassolisolucoes commented on Nov 5, 2025

    @cassolisolucoes
    cassolisolucoes
    on Nov 5, 2025

    Hey guys!
    For those ones the last version is not working, in my .env i just clear the version(empty) of webwhatsapp and work it!

  26. cleiton1982 commented on Nov 17, 2025

    @cleiton1982
    cleiton1982
    on Nov 17, 2025

    2.3000.1028401180

    gerou o qrcode, mas nao conecta. fica carregando no celular, na evolution mostra que conectou, mas logo cai

  27. cleiton1982 commented on Nov 17, 2025

    @cleiton1982
    cleiton1982
    on Nov 17, 2025

    2.3000.1028401180

    gerou o qrcode, mas não conecta. fica carregando no celular, na evolução mostra que conectou, mas logo cai

    para quem estiver com o mesmo problema, leia o qrcode, começou a ler feche o whatsap no celular que vai funcionar. pra mim resolveu assim

  28. lrebola commented on Nov 18, 2025

    @lrebola
    lrebola
    on Nov 18, 2025

    2.3000.1028401180

    gerou o qrcode, mas nao conecta. fica carregando no celular, na evolution mostra que conectou, mas logo cai

    Updating the Docker image to version 2.3.6 worked for me, and it also worked without CONFIG_SESSION_PHONE_VERSION.

  29. hellojoaovinicius commented on Jan 14, 2026

    @hellojoaovinicius
    hellojoaovinicius
    on Jan 14, 2026

    Estou com mesmo problema com qr code, a config session que estou usando é a 2.3000.1028401180 e meu docker é a versão 4.56.0, preciso de uma ajuda

  30. matheuscsant commented on Jan 15, 2026

    @matheuscsant
    matheuscsant
    on Jan 15, 2026

    Hey guys! For those ones the last version is not working, in my .env i just clear the version(empty) of webwhatsapp and work it!

    Funcionou pra mim também, limpar a versão consegui gerar o QRCode

  31. jeanlima94 commented on Feb 25, 2026

    @jeanlima94
    jeanlima94
    on Feb 25, 2026

    updating version to 2.3000.1033994345

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions