# Error: Command "start" not found **URL:** \ **Category:** Questions\ **Tags:** core, deployment\ **Created:** [July 18, 2025, 7:35pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129 "2025-07-18T19:35:10Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![semighoti](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@semighoti](https://community.n8n.io/u/semighoti)\ **Post date:** [July 18, 2025, 7:35pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/1 "2025-07-18T19:35:10Z")
Hi guys, I am running the latest N8N docker compose on portainer OMV NAS, and I got this error. I asked ChatGPT and it said that the new version does not have the command start. Any advice? Edit, I am running Queue mode and I have 2 workers on it. error | Error: Command “start” not found {“file”:“command-registry.js”,“function”:“execute”} ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [July 18, 2025, 7:37pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/2 "2025-07-18T19:37:37Z")
Where did you get this error? What did you do to get this error? How often does this error happen? Which version of n8n are you running? What are you trying to do? Can you share the workflow? ---
**Author:** ![semighoti](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@semighoti](https://community.n8n.io/u/semighoti)\ **Post date:** [July 18, 2025, 7:43pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/3 "2025-07-18T19:43:04Z")
Hi @jabbson, thank you for your response. I got this error in the docker logs. I just pulled the latest docker image, and went through the normal update process, then suddenly N8N is not working. I then went to check the docker logs, and that’s error. I could not access to the N8N interface, so I did not know what the version is ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [July 18, 2025, 7:45pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/4 "2025-07-18T19:45:16Z")
When you say “the latest” do you mean the tag `:latest` or the tag `:next`? ---
**Author:** ![semighoti](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@semighoti](https://community.n8n.io/u/semighoti)\ **Post date:** [July 18, 2025, 7:51pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/5 "2025-07-18T19:51:41Z")
it’s the `:latest` tag in the docker compose file ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [July 18, 2025, 8:13pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/6 "2025-07-18T20:13:44Z")
If you haven’t deleted the old image, does changing back to the old one fixes the problem? At least for you to export the workflows and credentials? ---
**Author:** ![semighoti](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@semighoti](https://community.n8n.io/u/semighoti)\ **Post date:** [July 18, 2025, 8:17pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/7 "2025-07-18T20:17:22Z")
Hi @jabbson, I have tried your suggestion, still have the same error. Even with the one before the previous one. ---
**Author:** ![semighoti](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@semighoti](https://community.n8n.io/u/semighoti)\ **Post date:** [July 18, 2025, 10:52pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/8 "2025-07-18T22:52:14Z")
Hi guys, I got a solution for the issue. It turns out that I did not give the right permission for subfolder. I should have given them the recursive -R when I do chmod command, lol. ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [July 18, 2025, 10:57pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/9 "2025-07-18T22:57:53Z")
I thought you only updated the image? How did your subfolder have different set of permissions after you pulled a new image? ---
**Author:** ![semighoti](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@semighoti](https://community.n8n.io/u/semighoti)\ **Post date:** [July 18, 2025, 11:14pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/10 "2025-07-18T23:14:55Z")
HI @jabbson, I am not sure what happened, but I did mess around permission for other apps, not N8N specifically because it is running some important workflows. I am using OMV NAS, so my guess is that I accidentally messed up the permission for N8N, but it had not got affected yet, and when I updated the image to the latest version (need set the container down), the new permission took effective. I need to document this issue for future use. ---
**Author:** ![itsgiff](https://avatars.discourse-cdn.com/v4/letter/i/73ab20/32.png) [@itsgiff](https://community.n8n.io/u/itsgiff)\ **Post date:** [July 22, 2025, 4:16pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/11 "2025-07-22T16:16:30Z")
what are the desired permissions? I am getting the same issue and I have the folder permissions the same as my other container. ---
**Author:** ![Nicholas\_Harvey](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/nicholas_harvey/32/59963_2.png) [@Nicholas\_Harvey](https://community.n8n.io/u/Nicholas_Harvey)\ **Post date:** [July 23, 2025, 12:08pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/12 "2025-07-23T12:08:38Z")
I ended up just adding --user root to the docker run command I was using. ---
**Author:** ![semighoti](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@semighoti](https://community.n8n.io/u/semighoti)\ **Post date:** [July 23, 2025, 3:52pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/13 "2025-07-23T15:52:19Z")
I give user:group-user permission to the N8N folders. Any user that has root privilege works, and the group is the user group on my NAS. OMV behaves a little bit strange to me. Even though I assign a user to the container, it appears that the delegation does not work accordingly. ---
**Author:** ![itsgiff](https://avatars.discourse-cdn.com/v4/letter/i/73ab20/32.png) [@itsgiff](https://community.n8n.io/u/itsgiff)\ **Post date:** [July 23, 2025, 6:22pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/14 "2025-07-23T18:22:48Z")
I have tried a few different permission models and can’t see to get this to stand up. It’s definitely not a standard container. ---
**Author:** ![semighoti](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@semighoti](https://community.n8n.io/u/semighoti)\ **Post date:** [July 23, 2025, 6:35pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/15 "2025-07-23T18:35:28Z")
Did you also do -R recursive the whole N8N folder when you set permission? ---
**Author:** ![itsgiff](https://avatars.discourse-cdn.com/v4/letter/i/73ab20/32.png) [@itsgiff](https://community.n8n.io/u/itsgiff)\ **Post date:** [July 23, 2025, 8:06pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/16 "2025-07-23T20:06:11Z")
yes, I did ---
**Author:** ![eldagninoai](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/eldagninoai/32/58864_2.png) [@eldagninoai](https://community.n8n.io/u/eldagninoai)\ **Post date:** [July 23, 2025, 8:35pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/17 "2025-07-23T20:35:06Z")
This is the correct solution ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [July 30, 2025, 8:35pm UTC](https://community.n8n.io/t/error-command-start-not-found/152129/18 "2025-07-30T20:35:40Z")
Closed on July 30, 2025, 8:35pm UTC This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.