# Unable to re-enable Execute Command node in n8n 2.0 using documented environment variables **URL:** \ **Category:** Questions\ **Created:** [December 19, 2025, 8:36am UTC](https://community.n8n.io/t/unable-to-re-enable-execute-command-node-in-n8n-2-0-using-documented-environment-variables/238232 "2025-12-19T08:36:23Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![etim808](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/etim808/32/146204_2.png) [@etim808](https://community.n8n.io/u/etim808)\ **Post date:** [December 19, 2025, 8:36am UTC](https://community.n8n.io/t/unable-to-re-enable-execute-command-node-in-n8n-2-0-using-documented-environment-variables/238232/1 "2025-12-19T08:36:23Z")
After upgrading to n8n 2.0, the Execute Command node is disabled by default as per the [breaking changes documentation](https://docs.n8n.io/2-0-breaking-changes/#disable-executecommand-and-localfiletrigger-nodes-by-default). I’ve attempted to re-enable the node using the `N8N_NODES_INCLUDE` environment variable as suggested, but the node still does not appear in the node selector. **Environment:** - n8n version: 2.0 - Installation method: System install (npm global) with systemd service - OS: Linux (Debian-based) **Steps to reproduce:** 1. Fresh n8n 2.0 install or upgrade from 1.x 2. Add `N8N_NODES_INCLUDE=n8n-nodes-base.executeCommand` to environment file (`/opt/n8n.env`) 3. Restart n8n via `sudo systemctl restart n8n` 4. Search for “Execute Command” in node panel — node does not appear ---
**Author:** ![Michael-o](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/michael-o/32/158575_2.png) [@Michael-o](https://community.n8n.io/u/Michael-o)\ **Post date:** [December 19, 2025, 8:39am UTC](https://community.n8n.io/t/unable-to-re-enable-execute-command-node-in-n8n-2-0-using-documented-environment-variables/238232/2 "2025-12-19T08:39:48Z")
This is expected in n8n 2.0. The **Execute Command** node is disabled by default for security reasons. If it’s still not showing, it usually means the setting isn’t being applied to the running instance or the service wasn’t fully restarted after the change. Please double-check where n8n is hosted and ensure the instance restarted correctly. 👉 If you want, tell me how you’re running n8n and I’ll help you fix it quickly. ---
**Author:** ![etim808](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/etim808/32/146204_2.png) [@etim808](https://community.n8n.io/u/etim808)\ **Post date:** [December 19, 2025, 10:48am UTC](https://community.n8n.io/t/unable-to-re-enable-execute-command-node-in-n8n-2-0-using-documented-environment-variables/238232/3 "2025-12-19T10:48:27Z")
I am running n8n in systemd on Debian LXC ---
**Author:** ![etim808](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/etim808/32/146204_2.png) [@etim808](https://community.n8n.io/u/etim808)\ **Post date:** [December 20, 2025, 7:11am UTC](https://community.n8n.io/t/unable-to-re-enable-execute-command-node-in-n8n-2-0-using-documented-environment-variables/238232/4 "2025-12-20T07:11:38Z")
please see reply, ty ---
**Author:** ![etim808](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/etim808/32/146204_2.png) [@etim808](https://community.n8n.io/u/etim808)\ **Post date:** [December 20, 2025, 7:35am UTC](https://community.n8n.io/t/unable-to-re-enable-execute-command-node-in-n8n-2-0-using-documented-environment-variables/238232/5 "2025-12-20T07:35:02Z")
I found solution: Add: _`NODES_EXCLUDE="[]"`_ To: opt/n8n.env github feedback: _Note that the exact environment variable required is as follows: `NODES_EXCLUDE="[]"`. After adding this variable, you should be able to see the nodes that were disabled by default in the nodes panel._ ---
**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:** [March 20, 2026, 7:35am UTC](https://community.n8n.io/t/unable-to-re-enable-execute-command-node-in-n8n-2-0-using-documented-environment-variables/238232/6 "2026-03-20T07:35:41Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.