API retornando Connection Closed na versão 2.2.3

[JonathanLopes404]

Welcome!

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

What did you do?

Estou enviando requests para a rota chat/whatsappNumbers e para a rota message/sendText

A API às vezes ta retornando sucesso, e às vezes retorna um erro 500 com esse body:
{"status":500,"error":"Internal Server Error","response":{"message":"Connection Closed"}}

Quando ele dá esse erro, a instância fica com status connecting por um tempo e depois volta ao normal.
Esse erro é temporário. Aparece, depois some, depois volta denovo...

E não é problema no número conectado na instância, a gente fez o teste no whatsapp, o número tava funcionando normalmente

What did you expect?

Resposta com status 200

What did you observe instead of what you expected?

Resposta com erro 500 e com o body:
{"status":500,"error":"Internal Server Error","response":{"message":"Connection Closed"}}

Screenshots/Videos

No response

Which version of the API are you using?

2.2.3

What is your environment?

Linux

Other environment specifications

No response

If applicable, paste the log output

2025-03-05T19:37:05.123087074Z �[1m�[31m[Evolution API]�[0m �[1m�[31m �[1m�[31m v2.2.3 �[1m�[31m 31 �[0m �[1m�[31m - �[1m�[37m Wed Mar 05 2025 16:37:05 �[0m �[31m�[41m�[1m ERROR �[0m �[33m�[1m [unhandledRejection]�[0m �[31m�[1m [object]�[0m �[31m �[0m
2025-03-05T19:37:05.123694181Z {
2025-03-05T19:37:05.123714481Z origin: Promise {
2025-03-05T19:37:05.123719381Z Error: Timed Out
2025-03-05T19:37:05.123723681Z at /evolution/node_modules/baileys/lib/Utils/generics.js:170:32 {
2025-03-05T19:37:05.123727581Z data: [Object],
2025-03-05T19:37:05.123730981Z isBoom: true,
2025-03-05T19:37:05.123734381Z isServer: false,
2025-03-05T19:37:05.123737781Z output: [Object]
2025-03-05T19:37:05.123741181Z }
2025-03-05T19:37:05.123744481Z },
2025-03-05T19:37:05.123747881Z stderr: 2
2025-03-05T19:37:05.123751281Z }
2025-03-05T19:37:05.123754581Z
2025-03-05T19:37:05.123757981Z �[1m�[31m[Evolution API]�[0m �[1m�[31m �[1m�[31m v2.2.3 �[1m�[31m 31 �[0m �[1m�[31m - �[1m�[37m Wed Mar 05 2025 16:37:05 �[0m �[31m�[41m�[1m ERROR �[0m �[33m�[1m [unhandledRejection]�[0m �[31m�[1m [object]�[0m �[31m �[0m
2025-03-05T19:37:05.123781382Z Error: Timed Out
2025-03-05T19:37:05.123785582Z at /evolution/node_modules/baileys/lib/Utils/generics.js:170:32 {
2025-03-05T19:37:05.123789182Z data: {
2025-03-05T19:37:05.123792482Z stack: 'Error\n' +
2025-03-05T19:37:05.123796082Z ' at promiseTimeout (/evolution/node_modules/baileys/lib/Utils/generics.js:165:19)\n' +
2025-03-05T19:37:05.123799782Z ' at waitForMessage (/evolution/node_modules/baileys/lib/Socket/socket.js:117:53)\n' +
2025-03-05T19:37:05.123803282Z ' at query (/evolution/node_modules/baileys/lib/Socket/socket.js:139:22)\n' +
2025-03-05T19:37:05.123806982Z ' at Object.executeUSyncQuery (/evolution/node_modules/baileys/lib/Socket/usync.js:62:30)\n' +
2025-03-05T19:37:05.123810582Z ' at Object.onWhatsApp (/evolution/node_modules/baileys/lib/Socket/chats.js:122:36)\n' +
2025-03-05T19:37:05.123814182Z ' at Rs.whatsappNumber (/evolution/dist/main.js:251:1191)\n' +
2025-03-05T19:37:05.123817682Z ' at async Kt.whatsappNumber (/evolution/dist/main.js:2:7612)\n' +
2025-03-05T19:37:05.123872083Z ' at async Ui.dataValidate (/evolution/dist/main.js:286:62716)\n' +
2025-03-05T19:37:05.123878783Z ' at async /evolution/dist/main.js:286:115236'
2025-03-05T19:37:05.123882383Z },
2025-03-05T19:37:05.123885783Z isBoom: true,
2025-03-05T19:37:05.123889083Z isServer: false,
2025-03-05T19:37:05.123892583Z output: {
2025-03-05T19:37:05.123895883Z statusCode: 408,
2025-03-05T19:37:05.123899183Z payload: {
2025-03-05T19:37:05.123902583Z statusCode: 408,
2025-03-05T19:37:05.123905983Z error: 'Request Time-out',
2025-03-05T19:37:05.123909383Z message: 'Timed Out'
2025-03-05T19:37:05.123912783Z },
2025-03-05T19:37:05.123916883Z headers: {}
2025-03-05T19:37:05.123920383Z }
2025-03-05T19:37:05.123923683Z }
2025-03-05T19:37:05.123926983Z

Additional Notes

No response

[marcogaruthix]

I'm also facing this behavior. I have to restart the instance but it doesn't an acceptable solution.
In my case using proxy feature, I'm wornder if it is a connection problem

[viniciustrndd]

Também estou tendo esse problema, a conexão cai por um tempo e depois normaliza sozinho. Só que nesse meio tempo dá erro nos meus agentes.