Because it stopped working or pairing code?

[maickom88]

Welcome!

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

What did you do?

From nothing, the pairing code stopped working, it doesn't work anymore like before. As you still generate the code when including it on WhatsApp, it gives it as an invalid code.

What did you expect?

Correct the code to pair

What did you observe instead of what you expected?

Correct the code to pair

Screenshots/Videos

No response

Which version of the API are you using?

2.2.3

What is your environment?

Windows

Other environment specifications

No response

If applicable, paste the log output

No response

Additional Notes

No response

[henrique-nhrl]

Realmente parou de funcionar. Tenho varias instalaçẽos e todas pararam.

[brunaagathaph1]

Minha aplicação é mobile e uso somente o codgo pra se conectar. Agora pagou tudo.

[JuniorrMacedo]

Estou enfrentando o mesmo problema: nenhuma aplicação está conseguindo se conectar via pairing code. Inclusive, o aviso que costumava aparecer no aplicativo do WhatsApp, informando sobre a tentativa de conexão, também deixou de ser exibido.

[VitorS0uza]

tambem mesmo problema. pairing code nao funciona

[JonathanLopesM]

Aqui também parou, estou atrás de uma versão que siga funcionando. testei até a v2.2.1, não lembro qual versão estava pois estava :latest no compose. se alguém puder ajudar...

[cendyandreoli]

Any updates on the issue? Was it due to a WhatsApp policy change? Is there any fix mapped out? Has anyone managed to work around it in another version?

[cendyandreoli]

this issue are fixed on Baileys https://github.com/WhiskeySockets/Baileys/issues/1448

[NieriDantas]

Alguem conseguiu entender o motivo ? conseguiram resolver?

[dpaes]

if what @cendyandreoli says its working on 6.7.17 of baileys, in the newest version of evolution api will work paircode fine. try to use develop version or docker hub evoapicloud/evolution-api:homolog (its 2.3.0 in development). @maickom88 @henrique-nhrl @brunaagathaph1 @JuniorrMacedo @VitorS0uza @JonathanLopesM @cendyandreoli @NieriDantas

[RenanAmaro]

I'm facing the same issue. I'm using version 2.2.3, but it still doesn't work. The code is generated, but I get an error when trying to use it in WhatsApp. Has anyone found an alternative solution?

[dpaes]

@RenanAmaro cant be 2.3.3 version, the last deploy version its 2.2.3, and the develop version its 2.3.0. read my last message, its the answer

[JonathanLopesM]

if what @cendyandreoli says its working on 6.7.17 of baileys, in the newest version of evolution api will work paircode fine. try to use develop version or docker hub evoapicloud/evolution-api:homolog (its 2.3.0 in development). @maickom88 @henrique-nhrl @brunaagathaph1 @JuniorrMacedo @VitorS0uza @JonathanLopesM @cendyandreoli @NieriDantas

I'll test it next, if it works I'll let you know

[afcasasfranco]

Same her on Docker, not show QR codes

[luimatheo99]

I tested it in version 2.2.3 and in the homologated version, but the pairingCode is still not connecting.

[afcasasfranco]

Cambie de la version 2.2.3 a la version 2.3.0 y aun asi no se genera QR y a su vez no hace paringCode

Pude solucionar colocando en el .env lo siguiente, eso si borre memoria redis Postgres y archivos de persistencia de Docker.

CONFIG_SESSION_PHONE_VERSION=2.3000.1023204200

[afcasasfranco]

I tested it in version 2.2.3 and in the homologated version, but the pairingCode is still not connecting.

Put on your .env this variable and reboot or erase databases

CONFIG_SESSION_PHONE_VERSION=2.3000.1023204200

[luimatheo99]

Testei na versão 2.2.3 e na versão homologada, mas o pairingCode continua não conectando.

Coloque no seu .env esta variável e reinicie ou apague os bancos de dados

CONFIG_SESSION_PHONE_VERSÃO=2.3000.1023204200

@afcasasfranco the problem here is the pairingCode, qrcode is working normally.

[pedrormc]

mine is not showing any qr code, but also when I try to send a message it shows me this error:

"message": "500 - "{"status":500,"error":"Internal Server Error","response":{"message":["Error: Timed Out"]}}"", "name": "AxiosError", "stack": "AxiosError: Request failed with status code 500\n at settle (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]/node_modules/axios/lib/core/settle.js:19:12)\n at RedirectableRequest.handleResponse (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]/node_modules/axios/lib/adapters/http.js:547:9)\n at RedirectableRequest.emit (node:events:536:35)\n at RedirectableRequest._processResponse (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]/node_modules/follow-redirects/index.js:398:10)\n at ClientRequest.RedirectableRequest._onNativeResponse (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]/node_modules/follow-redirects/index.js:91:12)\n at Object.onceWrapper (node:events:639:26)\n at ClientRequest.emit (node:events:524:28)\n at HTTPParser.parserOnIncomingClient (node:http_client:702:27)\n at HTTPParser.parserOnHeadersComplete (node:http_common:118:17)\n at Socket.socketOnData (node:http_client:544:22)\n at Axios.request (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]/node_modules/axios/lib/core/Axios.js:45:41)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at invokeAxios (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:206:10)\n at proxyRequestToAxios (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:656:20)\n at Object.request (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1698:4)", "code": "ERR_BAD_RESPONSE", "status": 500

[afcasasfranco]

Testei na versão 2.2.3 e na versão homologada, mas o pairingCode continua não conectando.

Coloque no seu .env esta variável e reinicie ou apague os bancos de dados CONFIG_SESSION_PHONE_VERSÃO=2.3000.1023204200

@afcasasfranco the problem here is the pairingCode, qrcode is working normally.

Maybe if delete databases?

[pedrormc]

it worked, thanks

[NieriDantas]

Testei na versão 2.2.3 e na versão homologada, mas o pairingCode continua não conectando.

Coloque no seu .env esta variável e reinicie ou apague os bancos de dados CONFIG_SESSION_PHONE_VERSÃO=2.3000.1023204200

@afcasasfrancoo problema aqui é o pairingCode, o qrcode está funcionando normalmente.

to na mesma amigo!! tenho uma aplicação em produção dependendo da funcionalidade de codigo numerico de pareamento!, QR code ta gerando deboa!!

[cendyandreoli]

[SOLUTION] Guys, I create a new image with the stable version of Baileys and It's working https://hub.docker.com/r/cendyandreoli/evolution-api

[McNickSisto]

CONFIG_SESSION_PHONE_VERSÃO=2.3000.1023204200 This solved the QR code not being generated. However, when scanning it I get a WhatsApp error : "cannot link new devices at this time". I tried with both professional and personal WhatsApp.

Then, when I tried generating the code, it does not work. Any news / thoughts ?

[NieriDantas]

[SOLUÇÃO] Pessoal, criei uma nova imagem com a versão estável do Baileys e está funcionando https://hub.docker.com/r/cendyandreoli/evolution-api

ola amigo! isso resolveu o problema de codigo de pareamento?

[agenciageraleads]

por aqui nada também usando a versao 2.2.3, gera o codigo mas nunca dá certo de conectar.

[JonathanLopesM]

[SOLUTION] Guys, I create a new image with the stable version of Baileys and It's working https://hub.docker.com/r/cendyandreoli/evolution-api

Cool, what did you need to change? Did you just change the Baileys package?