# I followed a question and tried to disable a base node using nodes\_exclude. But its not getting hidden

**URL:** <https://community.n8n.io/t/i-followed-a-question-and-tried-to-disable-a-base-node-using-nodes-exclude-but-its-not-getting-hidden/20391>\
**Category:** Questions\
**Tags:** node\
**Created:** [December 2, 2022, 6:32am UTC](https://community.n8n.io/t/i-followed-a-question-and-tried-to-disable-a-base-node-using-nodes-exclude-but-its-not-getting-hidden/20391 "2022-12-02T06:32:24Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mahesh\_Thiru](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mahesh_thiru/32/23141_2.png) [@Mahesh\_Thiru](https://community.n8n.io/u/Mahesh_Thiru)\
**Post date:** [December 2, 2022, 6:32am UTC](https://community.n8n.io/t/i-followed-a-question-and-tried-to-disable-a-base-node-using-nodes-exclude-but-its-not-getting-hidden/20391/1 "2022-12-02T06:32:24Z")

</div>

I tried hiding my error using nodes\_exclude environment variable in my docker -compose.yml. I also followed the below question and executed the steps. But still I am unable to hide it from the UI.

> [@How to disable n8n nodes available by default?](http://community.n8n.io/t/how-to-disable-n8n-nodes-available-by-default/18168/9):
>
> Hi @marcus, I am using the command docker run -it --rm -p 5678:5678 --name n8n -e NODES\_EXCLUDE=‘[“n8n-nodes-base.executeCommand”,“n8n-nodes-base.ssh”]’ n8nio/n8n:0.195.5 to disable the nodes. But nodes are still there. I am attaching the .env file. Please guide me if I am making any mistake while adding the command in .env file Thanks & Regards, Abhilash

The Node is not getting hidden in the UI. Please suggest what I had to do. I was trying to disable /hide aws ses. n8n-nodes-base.awsSes

---

<div class="post-metadata">

**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\
**Post date:** [December 5, 2022, 3:02pm UTC](https://community.n8n.io/t/i-followed-a-question-and-tried-to-disable-a-base-node-using-nodes-exclude-but-its-not-getting-hidden/20391/2 "2022-12-05T15:02:56Z")

</div>

Hi @Mahesh_Thiru, welcome to the community!

I am very sorry to hear you are having trouble. I just gave this a go on my end and was able to reproduce the problem. I can no longer exclude a node using something like `docker run -it --rm --name n8n -p 5678:5678 -e NODES_EXCLUDE='["n8n-nodes-base.awsSes"]' n8nio/n8n:0.205.0`:

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/b/6/b6baed3e219eb63113bbb06935270e377eba35a1.png)

Trying this on an earlier version of n8n (such as 0.203.1 using `docker run -it --rm --name n8n -p 5678:5678 -e NODES_EXCLUDE='["n8n-nodes-base.awsSes"]' n8nio/n8n:0.203.1`) still works:

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/7/2/72c781d69406c68c32d853f667aa8282dc6647ab.png)

I suspect this might be related to the changes around lazy-loading nodes in an attempt to use less memory. I shall add this to our engineering backlog for a closer look, perhaps you might want to downgrade to a slightly older version of n8n in the meantime?

---

<div class="post-metadata">

**Author:** ![Mahesh\_Thiru](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mahesh_thiru/32/23141_2.png) [@Mahesh\_Thiru](https://community.n8n.io/u/Mahesh_Thiru)\
**Post date:** [December 6, 2022, 4:31am UTC](https://community.n8n.io/t/i-followed-a-question-and-tried-to-disable-a-base-node-using-nodes-exclude-but-its-not-getting-hidden/20391/4 "2022-12-06T04:31:27Z")

</div>

Greetings @MutedJam. Thank you for the response. As a temporary work around i will be using v0.203.1. Please let me know if there is a newsletter or something similar where I can be notified once the bug is fixed or about new features.

---

<div class="post-metadata">

**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\
**Post date:** [December 6, 2022, 8:02am UTC](https://community.n8n.io/t/i-followed-a-question-and-tried-to-disable-a-base-node-using-nodes-exclude-but-its-not-getting-hidden/20391/5 "2022-12-06T08:02:02Z")

</div>

We don’t have a release newsletter I am afraid, but we usually release a new version of n8n once per week. You might want to check out [n8n/CHANGELOG.md at master · n8n-io/n8n · GitHub](https://github.com/n8n-io/n8n/blob/master/CHANGELOG.md) for the latest changelog.

In addition, we usually link any pull request to the forum post and will notify you once a fix has been released. So as long as you receive forum notifications you should get a message for this.

Hope this helps!

---

<div class="post-metadata">

**Author:** ![Mahesh\_Thiru](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mahesh_thiru/32/23141_2.png) [@Mahesh\_Thiru](https://community.n8n.io/u/Mahesh_Thiru)\
**Post date:** [December 6, 2022, 8:58am UTC](https://community.n8n.io/t/i-followed-a-question-and-tried-to-disable-a-base-node-using-nodes-exclude-but-its-not-getting-hidden/20391/6 "2022-12-06T08:58:02Z")

</div>

Thank you very much. This helps.

---

<div class="post-metadata">

**Author:** ![jan](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jan/32/9_2.png) [@jan](https://community.n8n.io/u/jan)\
**Post date:** [December 7, 2022, 12:45pm UTC](https://community.n8n.io/t/i-followed-a-question-and-tried-to-disable-a-base-node-using-nodes-exclude-but-its-not-getting-hidden/20391/7 "2022-12-07T12:45:14Z")

</div>

Got released with `n8n@0.206.1`

---

<div class="post-metadata">

**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 7, 2023, 12:46pm UTC](https://community.n8n.io/t/i-followed-a-question-and-tried-to-disable-a-base-node-using-nodes-exclude-but-its-not-getting-hidden/20391/8 "2023-03-07T12:46:00Z")

</div>

Closed on March 7, 2023, 12:46pm UTC

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