The N8n Offline Deployment Process Is Slow to Open Workflows

Questions
,
1

Describe the problem/error/question

Issue with extremely slow workflow loading in offline deployment of n8n.

First, let me introduce my environment:
I have deployed n8n using Docker on an Ubuntu system, isolated from all external service requests in a local area network environment (which can be considered an offline environment).

What is the error message (if any)?

Current situation:
n8n has been successfully deployed and the platform is usable. However, the issue is that the first loading of workflows is extremely slow, taking a very long time (whether creating new workflows or loading existing ones).
After waiting for a long time, the logs report an error:

2025-09-15T08:24:13.2017	debug	Querying 	database for waiting executions
{"scopes":["waiting-executions"],"file":"wait-tracker.js","function":"getW
aitingExecutions"}
2025-09-15T08:24:44.595Z	error	connect ETIMEDOUT 104.26.12.187:443	{"fi
le":"error-reporter.js","function":"defaultReport"}
2025-09-15T08:24:44.595Z	error	connect ETIMEDOUT 104.26.12.187:443	f"fi
le":"error-reporter.js","function":"defaultReport"}
2025-09-15T08:24:44.596Z	error	Error while fetching community nodes:	co
nnect ETIMEDOUT 104.26.12.187:443	{"file":"strapi-utils.js","function":"pag
inatedRequest"}

I have tried adding many additional configurations when creating the n8n container, but none of them worked. I hope there is a way to resolve this issue by adding configurations. Secondly, is there a method to solve this problem by modifying the source code?

Please share your workflow

The Docker deployment command is:

docker run --it --rm --name n8n -p 5678:5678 \
-v n8n_data:/home/node/.n8n \
-e N8N_SECURE_COOKIE=false \
-e N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true \
-e N8N_LISTEN_ADDRESS=0.0.0.0 \
-e N8N_LOG_LEVEL=debug \
-e N8N_SKIP_UPDATE_CHECK=true \
-e N8N_SKIP_DB_CHECK=true \
-e N8N_COMMUNITY_NODES_ENABLED=false \
-e N8N_DISABLE_TELEMETRY=true \
-e N8N_VERSION_NOTIFICATIONS_ENABLED=false \
-e N8N_DIAGNOSTICS_ENABLED=false \
--user root docker.n8n.io/n8nio/n8n

Information on your n8n setup

  • n8n version: 1.105.4
  • Database (default: SQLite): no
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):Docker
  • Operating system:linux Ubuntu 20
2

hello @Rainbook

According to the logs, seems that n8n is not able to connect to 104.26.12.187

3

Yes, thank you very much for your reply. Because n8n is deployed in a network isolated environment, it is certain that it cannot connect to this IP address (domain name: telemetric. n8n. io). But what I want to achieve is that when I open the workflow, I won’t connect to this IP address. Can you please find a way to close the connection to this IP address?

4

@barn4k What I hope to achieve is that when I open the n8n workflow, I will not request a connection to this IP address, so as not to block it here and cause a very long wait time. Do you have any solutions?

5

I suppose you have a long waiting period because n8n is trying to reach its servers (e.g. the information about the actual version). And I don’t think that’ it’s possible to completely disable that behavior.

Deploying it in the isolated environment actually doesn’t make much sense, as the tool is intended to be used along with various external systems

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.