I am trying to run n8n locally, but once the build is complete, start the dev server and open the browser its unresponsive, and shows “page is unresponsive” . I even tried running it inside a container but same issue
Hey @Muhammad-Owais-Warsi !
How did you installed it?
Npm /Docker?
Can you show some images with what you see?
I would suggest following this tutorial:
I’m currently on wsl. Using docker I ran the container with the commands given in the setup readme.
docker volume create n8n_data
docker run -it --rm --name n8n -p 5678:5678 -v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8n
These are the logs
After this when I open the http://localhost:5678 this is the page I can see and it doesnt load at all.
I also tried running without docker using pnpm in that scenario I can see the memory hike in my system
Thanks, let me try this
Here are the logs when I try running with npx n8n
owais@DESKTOP-CFHRO0C:/mnt/c/Users/Muhammad Owais Warsi$ npx n8n
Permissions 0644 for n8n settings file /home/owais/.n8n/config are too wide. This is ignored for now, but in the future n8n will attempt to change the permissions automatically. To automatically enforce correct permissions now set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true (recommended), or turn this check off set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false.
Initializing n8n process
n8n ready on ::, port 5678
There are deprecations related to your environment variables. Please take the recommended actions to update your configuration:
- DB_SQLITE_POOL_SIZE -> Running SQLite without a pool of read connections is deprecated. Please set `DB_SQLITE_POOL_SIZE` to a value higher than zero. See: https://docs.n8n.io/hosting/configuration/environment-variables/database/#sqlite
- N8N_RUNNERS_ENABLED -> Running n8n without task runners is deprecated. Task runners will be turned on by default in a future version. Please set `N8N_RUNNERS_ENABLED=true` to enable task runners now and avoid potential issues in the future. Learn more: https://docs.n8n.io/hosting/configuration/task-runners/
- N8N_BLOCK_ENV_ACCESS_IN_NODE -> The default value of N8N_BLOCK_ENV_ACCESS_IN_NODE will be changed from false to true in a future version. If you need to access environment variables from the Code Node or from expressions, please set N8N_BLOCK_ENV_ACCESS_IN_NODE=false. Learn more: https://docs.n8n.io/hosting/configuration/environment-variables/security/
- N8N_GIT_NODE_DISABLE_BARE_REPOS -> Support for bare repositories in the Git Node will be removed in a future version due to security concerns. If you are not using bare repositories in the Git Node, please set N8N_GIT_NODE_DISABLE_BARE_REPOS=true. Learn more: https://docs.n8n.io/hosting/configuration/environment-variables/security/
[license SDK] Skipping renewal on init: license cert is not initialized
Version: 1.121.3
Editor is now accessible via:
http://localhost:5678
Press "o" to open in Browser.
For now I cant even start n8n, so this is not what I need for now
From the n8n logs I see that the instance started just with some warnings that shouldn’t affect the UI.
What is your problem actually?
The issue is, when I open up the instance on the browser, the ui never render, even if it renders its unresponsive I cant even able to open console.
Even if you clear caches or open the page from a incognito tab?
If not, clear all images from Docker, start again as in docs, the enter this command:
‘docker ps’
So to be sure everything starts and points to the right path.
Tell as well with version are you installing.
I tried opening it in incognito and it works, but was not updating on code changes.
So I cloned the repo again and build it from scratch, but now even the build gets failed 
Ok , I got your confusion now.
Since you want to try locally n8n, and not cloning the repo use the following commands to install trough npm :
- npm install n8n -g
- n8n # or: n8n start
pnpm is only relevant when you’re working on the n8n source code repo itself (the monorepo), not for a normal local install.
P.S
For installing and running n8n locally (not developing the n8n repo itself).
But you ca use Docker as well :
docker volume create n8n_data
docker run -it --rm
–name n8n
-p 5678:5678
-e GENERIC_TIMEZONE=“<YOUR_TIMEZONE>”
-e TZ=“<YOUR_TIMEZONE>”
-e N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true
-e N8N_RUNNERS_ENABLED=true
-v n8n_data:/home/node/.n8n
docker.n8n.io/n8nio/n8n
Or use the video that @moosa already shared with you.
I think you misunderstood me. I cloned the repo and ran the following commands
-
pnpm install -
pnpm build -
pnpm dev
after that I opened up the tab in incognito and got this interface , but now its says invlaid credentials.
Even though I tried with my actual credentials as well as mock.
1 Like
Ok them, now it’s clear.
If you managed to get it working but have problems to access, try reset credentials:
n8n user-management:reset
Or docker :
docker exec -u node -it n8n user-management:reset
Then restart your instance.
2 Likes
Ran into another issue now. My wsl automatically stops working once the build is complete.
In the image, we can see that I’m outof wsl environment.
To add here as well, the crash is dues to memory-intensive. 8GB RAM is often not enough, and the process can be killed due to running out of memory. The recommendation is to have at least 12–16GB of free RAM during the build process.
So, allocate to your WSL VM more resources.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.