i cant excute any code node ! ( a simple display message)
Task request timed out after 60 seconds
Your Code node task was not matched to a runner within the timeout period. This indicates that the task runner is currently down, or not ready, or at capacity, so it cannot service your task.
If you are repeatedly executing Code nodes with long-running tasks across your instance, please space them apart to give the runner time to catch up. If this does not describe your use case, please open a GitHub issue or reach out to support.
If needed, you can increase the timeout using the N8N_RUNNERS_TASK_REQUEST_TIMEOUT environment variable.
What is the error message (if any)?
n8n version
2.1.5 (Self Hosted)
Stack trace
Error: Task request timed out after 60 seconds at LocalTaskRequester.requestExpired (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:304:17) at LocalTaskRequester.onMessage (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:272:10) at TaskBroker.handleRequestTimeout (/usr/local/lib/
Please share your workflow
Share the output returned by the last node
n8n version
2.1.5 (Self Hosted)
Stack trace
Error: Task request timed out after 60 seconds at LocalTaskRequester.requestExpired (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:304:17) at LocalTaskRequester.onMessage (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:272:10) at TaskBroker.handleRequestTimeout (/usr/local/lib/Information on your n8n setup
Try the below docker compose which sets up a docker compose instance on n8n running in queue mode with runners enabled as external supporting both JS and Python.
Also make sure to read this VERY IMPORTANT notice about the changes with python in n8n v2. If you have existing python code nodes, you will need to make some changes
ValidationError: The âX-Forwarded-Forâ header is set but the Express âtrust proxyâ setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See Page Redirection for more information.
at Object.xForwardedForHeader (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:187:13)
at Object.wrappedValidations. [as xForwardedForHeader] (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:398:22)
at Object.keyGenerator (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:671:20)
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:724:32
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:704:5 {
code: âERR_ERL_UNEXPECTED_X_FORWARDED_FORâ,
help: âhttps://express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/â
}
Slow database query
Task runner connection attempt failed with status code 403
Task runner connection attempt failed with status code 403
timeout of 3000ms exceeded
Error while fetching community nodes: timeout of 3000ms exceeded
Task runner connection attempt failed with status code 403
Task runner connection attempt failed with status code 403
Task runner connection attempt failed with status code 403
Task runner connection attempt failed with status code 403
Task request timed out
Error: Task request timed out
at ErrorReporter.wrap (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/errors/error-reporter.ts:242:37)
at ErrorReporter.error (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/errors/error-reporter.ts:228:25)
at LocalTaskRequester.requestExpired (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:309:22)
at LocalTaskRequester.onMessage (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:272:10)
at TaskBroker.handleRequestTimeout (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker.service.ts:115:50)
at Timeout. (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker.service.ts:102:9)
at listOnTimeout (node:internal/timers:588:17)
at processTimers (node:internal/timers:523:7)
Task request timed out after 60 seconds
Task runner connection attempt failed with status code 403
Task runner connection attempt failed with status code 403
Task runner connection attempt failed with status code 403
Task runner connection attempt failed with status code 403
Can you first run my docker compose by itself without changing anything in it and confirm whether it works with the localhost settings as is. Stop any other n8n instances you have running to isolate the test. The 403 suggests that you have something else going on in the back which is causing the problem. Letâs first isolate the environment weâre testing
Yes, the more you mix configs on your side, the more moving parts there are, the less likely we are able to help you debug the problem. Remember we dont have a view into what you see, so the above tutorial with nginx is telling there is something else which could be causing this to break. I wanted you to run my compose file as is. Make sure to expose your port for now to test. Ignore the dns domain setup and anything additional for now. We can deal with that after the fact. I want us to first confirm whether you can host an instance with Python runner working. That is priority right now
Owner was set up successfully
ValidationError: The âX-Forwarded-Forâ header is set but the Express âtrust proxyâ setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See for more information.
at Object.xForwardedForHeader (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:187:13)
at Object.wrappedValidations. [as xForwardedForHeader] (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:398:22)
at Object.keyGenerator (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:671:20)
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:724:32
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:704:5 {
code: âERR_ERL_UNEXPECTED_X_FORWARDED_FORâ,
help: âhttps:/express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/â
}
ValidationError: The âX-Forwarded-Forâ header is set but the Express âtrust proxyâ setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See for more information.
at Object.xForwardedForHeader (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:187:13)
at Object.wrappedValidations. [as xForwardedForHeader] (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:398:22)
at Object.keyGenerator (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:671:20)
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:724:32
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:704:5 {
code: âERR_ERL_UNEXPECTED_X_FORWARDED_FORâ,
help: âhttps:/express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/â
}
(node:8) [DEP0060] DeprecationWarning: The util._extend API is deprecated. Please use Object.assign() instead.
(Use node --trace-deprecation ... to show where the warning was created)
ValidationError: The âX-Forwarded-Forâ header is set but the Express âtrust proxyâ setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See for more information.
at Object.xForwardedForHeader (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:187:13)
at Object.wrappedValidations. [as xForwardedForHeader] (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:398:22)
at Object.keyGenerator (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:671:20)
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:724:32
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:704:5 {
code: âERR_ERL_UNEXPECTED_X_FORWARDED_FORâ,
help: âhttps:/express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/â
}
ValidationError: The âX-Forwarded-Forâ header is set but the Express âtrust proxyâ setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See for more information.
at Object.xForwardedForHeader (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:187:13)
at Object.wrappedValidations. [as xForwardedForHeader] (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:398:22)
at Object.keyGenerator (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:671:20)
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:724:32
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:704:5 {
code: âERR_ERL_UNEXPECTED_X_FORWARDED_FORâ,
help: âhttps:/express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/â
}
User survey updated successfully
User attempted to access a workflow without permissions
User attempted to access a workflow without permissions
timeout of 3000ms exceeded
Error while fetching community nodes: timeout of 3000ms exceeded
Enqueued execution 1 (job 1)
Blocked GET /robots.txt for âMozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36; compatible; OAI-SearchBot/1.3; robots.txt; +https://openai.com/searchbotâ
Slow database query
Enqueued execution 2 (job 2)
Please share your docker compose file and edit out any sensitive information such as secrets.
The mention of âThe âX-Forwarded-Forâ headerâ tells me youâre still going through nginx somewhere. Are you running this locally on your PC and not the server?
Same issue for me - just running locally.
Trying with a minimal reproducible example: single n8n container, single runner container, no redis no postgres.
Set up was working pyodide and python native with v1.
If youâre not using queue mode which requires worker instances, then make sure you update your runnerâs broker env var to point to ân8n-mainâ and not worker