Recebimento de mídia no Chatwoot falha com erro "Text is required"

[rogeriolixa]

Welcome!

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

What did you do?

Olá, equipe da Evolution API.

Estou enfrentando um bug persistente onde o recebimento de arquivos de mídia (como imagens, vídeos, etc.) de um contato do WhatsApp não é processado corretamente na integração com o Chatwoot.

Enquanto mensagens de texto são recebidas normalmente, qualquer arquivo de mídia que chega aciona um erro 400 Bad Request. Confirmei que este problema ocorreu tanto na versão v2.2.1 quanto na v2.3.1, mesmo após ter atualizado a minha instância.

What did you expect?

Comportamento Esperado:
A imagem enviada pelo WhatsApp deveria aparecer corretamente como um anexo de mídia dentro da conversa no Chatwoot.

What did you observe instead of what you expected?

Comportamento Atual:
A imagem não aparece no Chatwoot. Em vez disso, a Evolution API registra um erro 400 Bad Request: Text is required e uma nota privada de erro é criada na conversa do Chatwoot.

Screenshots/Videos

No response

Which version of the API are you using?

Evolution Api
v2.3.1 (atual)
v2.3.0 (testado - mesmo erro)
v2.2.3 (testado - mesmo erro)
v2.2.1 (testado - mesmo erro)

Chatwoot
v4.0.1

What is your environment?

Windows

Other environment specifications

Ambiente Docker;
VMware - Linux;
ZeroTrust Cloudflare.

If applicable, paste the log output

Log da Evolution API (v2.3.0):

[Evolution API] v2.3.0 185 - Tue Jul 01 2025 10:26:57 LOG [ChannelStartupService] [object]
{
key: {
remoteJid: '[REDACTED_PHONE_NUMBER]@s.whatsapp.net',
fromMe: false,
id: '[REDACTED_WHATSAPP_ID]',
...
},
message: {
imageMessage: ImageMessage { ... }
},
messageType: 'imageMessage',
messageTimestamp: 1751376416,
instanceId: '[REDACTED_INSTANCE_ID]',
...
chatwootMessageId: XXXXX,
chatwootInboxId: XX,
chatwootConversationId: XX
}
[Evolution API] v2.3.0 185 - Tue Jul 01 2025 10:26:58 VERBOSE [ChatwootService] [string] onSendMessageError {"status":400,"error":"Bad Request","message":["Text is required"]}
[Evolution API] v2.3.0 185 - Tue Jul 01 2025 10:26:58 ERROR [ChatwootService] [object]
{ status: 400, error: 'Bad Request', message: [ 'Text is required' ] }

Log do Chatwoot:

I, [2025-07-01T13:26:58.078387 #21] INFO -- : [REDACTED_REQUEST_ID] Parameters: {"content"=>"🚨 Não foi possível enviar a mensagem. Verifique sua conexão. [object Object]", "message_type"=>"outgoing", "private"=>"[FILTERED]", "account_id"=>"X", "conversation_id"=>"XX"}

Additional Notes

---

[dpaes]

vc consegue replicar o erro?

[erildobarone]

Conseguiu resolver?

[carnivash]

Estou com esse mesmo problema, a princípio achei que configurando o S3 iria resolver, mas não funcionou, eu vejo tanto o chatwoot quanto a evolutionapi colocando arquivos no bucket normalmente, mas o erro persiste, a única diferença entre meu setup e do autor @rogeriolixa é que o meu chatwoot está na v4.3.0
tem outro issue relatando esse mesmo problema: #1710

[erildobarone]

Resolvido, amigo era rota tunel clouflare alterei na stack para rodar Http

[wilerptech]

SOLVED: "Text is required" Error Caused by Multi-WAN Network Environment, Not a Bug

Hello everyone,

I wanted to share my experience with this issue, as I was experiencing the exact same symptoms: the "Text is required" error when receiving media files without a caption. However, after extensive testing, I discovered the root cause was not a bug in the Evolution API itself, but a network configuration issue in my local environment.

Summary of the Investigation:

Identical Symptoms: Just like the original report, my setup failed to process media files without text, while text messages worked perfectly.

Testing in a Clean Environment: I deployed the exact same setup (same versions of Evolution API and Chatwoot) on a clean AWS EC2 instance with a single public IP. In this environment, everything worked perfectly. This was the key step that proved the issue was related to my local network, not the software.

Local Environment Details: My local setup runs on Proxmox and uses an OPNsense firewall to manage the network. Crucially, I have a Multi-WAN configuration (two internet connections) for load balancing.

Root Cause: Asymmetric Routing: The problem was asymmetric routing caused by the Multi-WAN load balancing. When a media file was being transferred, the connection session was being split across my two different WAN links. As a result, packets were arriving at the destination server (WhatsApp's media server) from two different public IP addresses. For security reasons, the server would terminate the connection, causing the file transfer to fail.

The Definitive Solution: The issue was completely resolved when I disabled one of my WAN links in OPNsense, forcing all traffic through a single, stable route. This eliminated the asymmetric routing, and media files started working immediately.

I'm sharing this in detail because other users with complex network setups (like Multi-WAN for load balancing or failover) might be misdiagnosing this as a software bug. Standard fixes for Multi-WAN, like enabling "Sticky Connections" in OPNsense, did not solve the issue in my case, pointing to a more fundamental problem with how these complex sessions are handled in a load-balanced environment.

Hope this helps someone else save some time!

[muno3421]

alguem tem alguma solução? estou com o mesmo erro, o cloudflare esta como http e via traefik

[wigo007]

¡Hola! Después de investigar bastante, he encontrado para mi la causa exacta de este problema.

El culpable es el túnel de cloudflared. Parece que interfiere con las peticiones que envían archivos (de tipo multipart/form-data) y elimina los datos del archivo adjunto antes de que la petición llegue a Traefik. Por esta razón, Chatwoot devuelve el error "Text is required", porque la petición le llega incompleta, sin el archivo.

Cómo puedes confirmarlo:
Apunta el registro DNS en Cloudflare directamente a la IP pública de tu servidor, en lugar de usar el túnel. Cuando la conexión va directo a tu Traefik (sin pasar por cloudflared), el envío de archivos funciona perfectamente.

Solución:
Evita usar el túnel de cloudflared para este servicio. Configura tu DNS para que apunte directamente a tu IP pública.

[thiagoomatheus]

Alguma solução para servidor local com cloudflare tunnel?

[FIXONWEB]

Cloudflare tunnel:
No "Chatwoot URL" põe teu endereço IP local (fixo) e a porta ao invés do endereço público do Chatwoot.
Foi assim que consegui resolver, seguindo as dicas.
Depois disto, todas as mídias chegam no Chatwoot.