Attempt to read execution blocked due to insufficient permissions... again, sorry!

[fletcher]

Local File Trigger node won’t fire up

Yet my workflow is set to Active.
Note: when I test with a manual trigger (When clicking ‘Test workflow’), my workflow works well.

Error message: Attempt to read execution was blocked due to insufficient permissions

Output returned by the last node: none.

• The root user inside the container has access.
• Checked in the File Explorer properties: The user or group has Full Control and permissions are given all to way to subfolders.

My docker-compose.yml file:

version: "3.8"

services:
  n8n:
    image: n8nio/n8n:latest
    container_name: n8n
    user: root
    ports:
      - "5678:5678"
    volumes:
      - /c/Users/fred/Projects/git-pulls:/data/git-pulls

Information on your n8n setup

• **n8n version:**1.69.2
• **Database (default: SQLite):**SQLite
• **n8n EXECUTIONS_PROCESS setting (default: own, main):**own
• **Running n8n via (Docker, npm, n8n cloud, desktop app):**Docker desktop
• Operating system: Win 11 64bits

instance information

Debug info

core

• n8nVersion: 1.69.2
• platform: docker (self-hosted)
• nodeJsVersion: 20.18.0
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: enterprise (production)
• consumerId: 341d99a3-2fba-483e-ac4c-0e62ccc3e996

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/131.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2024-11-30T15:50:26.831Z

[netroy]

Do you by any chance have execution saving disabled for this workflow in the settings, or globally? if yes, can you please try enabling saving of successful executions, and see if that fixes the issue?

[fletcher]

Sorry it does not help either. I tried all scenarii before, with the Do not Save, Default - Save and Save options. File update won’t trigger the flow.

[fletcher]

Anyone willing to share insights on what’s happening with the " insufficient permissions" message?
My Local File Triggers don’t work.

[fletcher]

Sad to see no one sharing insights on this issue…
Maybe time to switch to Buildship?

[netroy]

The issue most likely is that you are running on Windows, which is making permissions setup even more complicated than it needs to be.
The folder on the host machine might be accessible to the Windows user, but n8n is running as UID 1000 inside a Linux container, inside a Linux VM, inside Windows.
I have no idea how to user ids map in setups like these, and I unfortunately do not have access to a setup like this to debug or provide any further assistance.

To be able to access your host files like this, your best option is either to probably run the (non-recommended) NPM setup, or find someone with a good understanding of docker on Windows to help you setup the permissions correctly.

@fletcher

Maybe time to switch to Buildship?

I’m not sure how statements like these are going to get you any help on any community forum.
If you are a paying customer, you should definitely reach out to [email protected] for official support. They could help prioritize this.

[fletcher]

Thanks, I will literally copy-paste your answer to o1 and some of customGPT trained on Dicker and will report on the outcome…

[fletcher]

So incredibly complexe that o1 can’t provide a consistent response.
Sadly, I’ll have to drop Docker. And I’ve just lost my workflow.

You’ve said npm is not recommended, yet it is one of the method in the n8n doc. Can you clarify why you do not recommend it?

[netroy]

Can you clarify why you do not recommend it

When one installs n8n from docker, the docker image contains a snapshot of all the dependencies. If they download the same version of the docker image 1 few months later, they will get the same exact software,

However when one installs n8n via npm, they get the dependencies as resolved by npm at the time of installation, which sometimes look different than the snapshots in the docker image. We’ve had these issues in the past that some dependency of a dependency made a breaking change without updating the version correctly and introduced new bugs on an old version of n8n.

Also, the docker image contains Linux packages that are needed for the proper functioning of some of the nodes like Git, or EditImage.
For npm, the user is expected to install those operating system packages.

Many users do use the NPM package, and it’s very likely that it’ll work for you just fine. It’s just that officially we only want to recommend docker for any production usage because it’s the only version where we can guarantee that n8n will work as shipped by us.

And I’ve just lost my workflow.

If you still have the docker container, you can either export the workflow from the frontend, or you can use the n8n cli from inside the container to export all workflows.

[fletcher]

FYI and for the future readers:

The Docker approach was so incredibly complexe (permission issues), that I drop it and reinstalled n8n with npm. Works very well and much faster than with Docker, and not a battery drainer.

Could n8n look into uv as a better package manager for installing/managing n8n?