Running Version: 1.77.3 running locally on OSX Monterey
Local File Trigger stalls out… it’s active
I ran fswatch in terminal - worked fine
I tried 777 chmod
Tried a number of things. Everything looks good locally, arrows pointing to Local File Trigger node
So…I found a thread on here suggesting it might be a Docker issue:
I went back to the npm/n8n route…Local File Trigger green for go. Loaded like a champ.
NOW…at the same time I also saw an error stating:
Permissions 0644 for n8n settings file /Users/bigdog/.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.
User settings loaded from: /Users/bigdog/.n8n/config
I asked Google Studio if this was relative or benign. It said it was routine and probably wasn’t the issue. So it might not be 100% Docker, but…after three days of struggling to get this any process running locally, I’m so sick of troubleshooting this. My vote is Docker was getting in the way somehow. If I’m wrong, or if there’s an update in the future, please feel free to update this thread.
I just wanted to ping this out so if somebody else starting out is having issues, this might be the issue. Chat and Studio both had me load Docker.
Just Sayin’, Thanks for reading!