Updating n8n on Windows Machine

Suratwala · December 2, 2021, 2:11am

Hi,

I have n8n installed on my Windows 10 and 11 machines. When I stop the service and run the update command, it sits there for a few seconds and nothing happens. But if I run the install command with a specific build, it works fine. I have been doing this for a few builds now and the update command has never worked for me. Every time I run the install command it resets all my config settings. Any help would be greatly appreciated.

mcnaveen · December 2, 2021, 6:37am

I’m not a Windows user. So, I don’t know what is happening. But I feel setting up with Docker is the best option Or try n8n desktop (Announcing the n8n desktop app)

MutedJam · December 2, 2021, 8:15am

Hi @Suratwala, I am sorry to hear you’re running into this issue.

Could you share some additional details here? What exactly is happening for you when saying the install resets all your config settings? Would it delete the .n8n\config file in your home directory?

As for the problem you are having with npm update I’m not sure it’s directly related to n8n tbh. In the npmjs registry, version 0.151.0 would have the latest tag as expected. Can you confirm which n8n versions npm outdated -g --depth=0 prints for you and what npm update -g -dd n8n returns on your machine (the -dd would set the log level to verbose)?

Also, is the behaviour the same for you when using the regular command prompt or MS PowerShell (I’m wondering if the environment in the prompt you are currently using might have something to do with this)?

Suratwala · December 2, 2021, 10:06am

Thank you @MutedJam for your response.

The config reset part was for when I used the install command to install the latest build as the update command does not work. I ran the commands that you suggested using cmd, cmd as administrator, PowerShell, and Node.js command prompt and got the same results:

If you need any other info, please let me know.

Suratwala · December 2, 2021, 10:12am

Hi again, @MutedJam,

I updated npm to the latest build and that fixed the issue.

Thank you so much for your help in diagnosing the issue.

MutedJam · December 2, 2021, 10:14am

I was just reading a similar suggestion at:

github.com/npm/cli

[BUG] npm update global not updating packages to latest

opened 11:01PM - 30 Jan 20 UTC

closed 09:55PM - 02 Jun 21 UTC

johnkennedy9147

Bug

Attempting to update all globally installed packages docs state should go to lat…est but this does not happen. Possibly updating as if applying semver ^ range. `npm outdated` shows: Package | Current | Wanted | Latest | Location --------|--|-----|----|--- eslint | 5.16.0 | 5.16.0| 6.8.0| global gatsby-cli | 2.8.21 | 2.8.28 |2.8.28| global lighthouse | 4.3.0 | 4.3.1| 5.6.0 |global prettier | 1.18.2 | 1.19.1| 1.19.1 |global rimraf | 2.6.3 | 2.7.1 | 3.0.1 | global yarn | 1.15.2 |1.21.1| 1.21.1 | global ran npm update `npm outdated` now shows Package | Current | Wanted | Latest | Location ----------------|---|------|---|-- eslint | 5.16.0 | 5.16.0 | 6.8.0 | global lighthouse | 4.3.1 |4.3.1| 5.6.0 | global Expectation was that both would have been updated to latest. eslint not updated. lighthouse only updated to highest V4 version published (consistent with semver ^)

But it seemed a bit generic so I was currently setting up a test environment on my end for this

Glad to hear you figured this out, thank you so much for confirming!

semighoti · December 2, 2021, 11:45pm

Hi @Suratwala, Did you install n8n on your window without docker? Could you please elaborate the process of the installation?

Suratwala · December 3, 2021, 8:08am

Hi @semighoti,

Yes, I am using it without Docker on Windows.

These are the steps from my notes, if you get stuck at any point, send me the error message and it may jog my memory.

Install Node.js
Run PowersShell as Administrator
Run npm install n8n -g
Update the npm version if available: e.g. npm install -g [email protected]
Run n8n - this will save the config and database.sqlite files to C:\Users\<UNSERNAME>\.n8n folder
If you see an EPERM Error on path C:\Windows\System32\LogFiles\WMI\RtBackup, change the OWNER on ‪C:\Windows\System32\LogFiles\WMI\RtBackup to EVERYONE
Remove Deny permission for Everyone and Add Allow permission for Everyone on C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache\Content.IE5
Delete database.sqlite from C:\Users\<USERNAME>\.n8n
Run n8n - if all goes well, this should show a message saying:

Editor is now accessible via:
http://localhost:5678/

index.js in folder C:\Users\<USERNAME>\AppData\Roaming\npm\node_modules\n8n\dist\config contains system config options.

All the best .

semighoti · December 3, 2021, 6:10pm

@Suratwala, Thank you so much, let me try it.

I have another question, How to change http://localhost:5678/ to https://mydomain.com to use webhooks and other authorizations?

Suratwala · December 4, 2021, 7:24pm

Hi @semighoti,

You are most welcome.

All customisation settings are in the index.js file located in folder C:\Users\<USERNAME>\AppData\Roaming\npm\node_modules\n8n\dist\config.

semighoti · December 4, 2021, 8:35pm

Thank you so much. I appreciate it very much.

michael75 · March 6, 2023, 9:01pm

Hello,
thanks for this post. It’s very helpfull!
I have an issue following your steps. Deployment is working and i have my n8n on http://localhost:5678 but when i start my workflow, it going at the end and never stop spinning… No error information on the console log and the workflow is runing well.

Do you have any idea how to fix that?

Thanks

Suratwala · March 6, 2023, 9:40pm

Hi @michael75, can you please take a screenshot and post? Have you tried a browser refresh and is it still spinning after that? Could be just a refresh issue. Try another browser or clear cache. Turn on save execution and also monitor the execution to see if it’s really running.

michael75 · March 7, 2023, 8:48am

Many thanks for your answer!

I did a video about it: Loom | Free Screen & Video Recording Software | Loom

Suratwala · March 7, 2023, 8:32pm

Hi @michael75,

Loom is down for maintenance so I can’t view your video but reading the release notes for the latest build, looks like it might have been a bug: “ * Prevent executions from displaying as running forever”. Try updating to the latest build and see if it fixes it.