Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

n8n tries to access "Anwendungsdaten" #4007

Closed
lublak opened this issue Sep 2, 2022 · 7 comments · Fixed by #4082
Closed

n8n tries to access "Anwendungsdaten" #4007

lublak opened this issue Sep 2, 2022 · 7 comments · Fixed by #4082

Comments

@lublak
Copy link
Contributor

lublak commented Sep 2, 2022

Describe the bug

I have had this strange error for a while. It still doesn't make sense to me and I currently use Linux under Windows to test things.
After I completely rebuilt my PC I thought I could try it again.
But as soon as you start n8n it looks for the folder "Anwendungsdaten" (German) which of course does not exist.
Note here "C:\Users" which is not German.

grafik

To Reproduce

Strangely enough, I can't mirror it on any computer. Unfortunately, I currently have no idea what the problem is and how to reproduce it. Since I have a completely rebuilt PC as well as another PC, it makes no sense.
I have already changed the language of the operating system and many other things.

Expected behavior

That it works the same way as on the other computers.

Environment (please complete the following information):

  • OS: Windows 10 Pro 21H2
  • n8n Version 0.193.3
  • Node.js Version v16.17.0
  • Database system SQLite
  • Operation mode own
@Joffcom
Copy link
Member

Joffcom commented Sep 2, 2022

Hey @lublak,

Thanks for reporting this one, I remember we had a quick chat about it on Discord and I have also not been able to reproduce it. @ivov do you have any thoughts on this one?

@Joffcom
Copy link
Member

Joffcom commented Sep 2, 2022

Hey @lublak,

Couple of questions for you that I don't think we covered before...

You said it is only this machine that has an issue, Is there anything different about it and how you use Node processes (sandbox, nvm)? Maybe a different AV or it is part of a domain / device management system? When you installed n8n what npm options did you use as well?

@lublak
Copy link
Contributor Author

lublak commented Sep 2, 2022

@Joffcom

Unfortunately not. I have the same installation of nodejs.
https://nodejs.org/dist/v16.17.0/node-v16.17.0-x64.msi
My computer at home is not in the domain (which has these problems), the one at work is in a domain.
npm install -g n8n
It is the only command I execute.
So nothing special here.

As long as no one else encounters this problem, we can just leave it as it is. I'm fine with Linux. And in the next few months I'll be getting a new private PC here, too. Maybe it will be functional there again.
Of course, it would be interesting to know what the problem is.

@Joffcom
Copy link
Member

Joffcom commented Sep 2, 2022

Hey @lublak,

That rules out some of the other options I thought it could be, I am going to get an internal ticket created so we can look into this a bit more as it is very strange. Any AV running on it or just Defender?

@lublak
Copy link
Contributor Author

lublak commented Sep 2, 2022

Just default windows defender

@netroy
Copy link
Member

netroy commented Sep 2, 2022

I suspect this ShellJS issue is the cause.

@netroy
Copy link
Member

netroy commented Sep 12, 2022

The ShellJS issue is unrelated to this. The issue here is how fast-glob works.
I've fixed this in #4082

valya pushed a commit to valya/n8n that referenced this issue Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants