Chat trigger response timeout after 1 minute and 30 seconds. #26971
Description
Bug Description
Chat trigger response timeout after 1 minute and 30 seconds. No known way to change this timeout timing. Setting N8N_WEBHOOK_TTL has no effect.
Error message
"<html>\r\n<head><title>504 Gateway Time-out</title></head>\r\n<body>\r\n<center><h1>504 Gateway Time-out</h1></center>\r\n<hr><center>openresty</center>\r\n</body>\r\n</html>\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n"
To Reproduce
- Base setup (Install RHEL 9, Docker, docker-compose.yml, persistent storage, Nginx Proxy Manager).
- Create a new workflow.
- Add a chat trigger.
- Build out a workflow that will run for longer than 1 minute 30 seconds (mine was an ai agent with a js code node with regex.
- Run the workflow and wait for > 1 minute 30 seconds.
Expected behavior
User configurable timeout variable for chat trigger (or underlying timeout mechanism).
Debug Info
Debug info
core
- n8nVersion: 2.11.3
- platform: docker (self-hosted)
- nodeJsVersion: 24.13.1
- nodeEnv: production
- database: postgres
- executionMode: regular
- concurrency: -1
- license: community
- consumerId: unknown
storage
- success: all
- error: all
- progress: false
- manual: true
- binaryMode: filesystem
pruning
- enabled: true
- maxAge: 336 hours
- maxCount: 10000 executions
client
- userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/145.0.0.0 safari/537.36
- isTouchDevice: false
Generated at: 2026-03-13T06:10:58.528Z
Operating System
RHEL 9
n8n Version
2.11.3
Node.js Version
24.13.1
Database
PostgreSQL
Execution mode
main (default)
Hosting
self hosted