Unable to get Local File Trigger

Questions
1

I am running the n8n via docker compose file

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n
    restart: always
    ports:
      - "127.0.0.1:5678:5678"
    environment:
      - N8N_HOST=${DOMAIN_NAME}
      - N8N_PORT=5678
      - N8N_PROTOCOL=http
      - NODE_ENV=production
      - WEBHOOK_URL=http://${DOMAIN_NAME}/
      - GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
      - TZ=${GENERIC_TIMEZONE}
      - NODES_EXCLUDE="[]"
    volumes:
      - n8n_data:/home/node/.n8n
      - ./local_files:/files

volumes:
  n8n_data:

I am unable to access the Local File Trigger. Did anyone get this working? The documentation on this is vague and unreliable.

2

Hi @Kaszanas, welcome

since n8n v2:

n8n will disable the ExecuteCommand and LocalFileTrigger nodes by default because they pose security risks. These nodes allow users to run arbitrary commands and access the file system.

Migration path: If you need to use these nodes, remove them from the disabled nodes list in your n8n configuration by updating the NODES_EXCLUDE environment variable. For example, set NODES_EXCLUDE="[]" to enable all nodes, or remove only the specific nodes you need.

1 Like
3

Please refer to my docker compose file. I already made this change.

      - NODES_EXCLUDE="[]"

This did not work. I have tried setting this via .env file as well.

4

If you’re using coolify try:

- 'NODES_EXCLUDE="[]"'
5

It turns out that the genius Google Chrome was caching the entire website even though I was refreshing.

I had to use a different browser.

1 Like
6

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