How to cleanup/remove broken custom nodes?

Describe the problem/error/question

2025-02-20T09:56:30.233357157Z Error removing package "@eavfw/n8n-nodes-eavfw":async function (requestOptions) {
2025-02-20T09:56:30.233377413Z                                 const selectedCategory = this.getNodeParamete...<omitted>... } could not be cloned.
2025-02-20T09:56:30.233379217Z ResponseError: Error removing package "@eavfw/n8n-nodes-eavfw":async function (requestOptions) {
2025-02-20T09:56:30.233380576Z                                 const selectedCategory = this.getNodeParamete...<omitted>... } could not be cloned.
2025-02-20T09:56:30.233381911Z     at CommunityPackagesController.uninstallPackage (/usr/local/lib/node_modules/n8n/dist/controllers/community-packages.controller.js:153:19)
2025-02-20T09:56:30.233383208Z     at processTicksAndRejections (node:internal/process/task_queues:95:5)
2025-02-20T09:56:30.233384470Z     at handler (/usr/local/lib/node_modules/n8n/dist/decorators/controller.registry.js:93:24)
2025-02-20T09:56:30.233385723Z     at /usr/local/lib/node_modules/n8n/dist/response-helper.js:110:26
2025-02-20T09:56:30.233395079Z 
2025-02-20T09:56:30.233395984Z async function (requestOptions) {
2025-02-20T09:56:30.233396858Z                                 const selectedCategory = this.getNodeParamete...<omitted>... } could not be cloned.

I got similar error “cant be cloned” when i tried to install my custom node and now i am trying to uninstall it in the ui and it gives error above.

How can i remove the node so i can try installing it again, and how to i find out why i get the cant be cloned error on both install /uninstall

Information on your n8n setup

  • n8n version:1.78.0
  • Database (default: SQLite):default
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):coolify/docker
  • Operating system:linux

This is the error when installing

2025-02-21T11:32:25.060793045Z Error loading package "@eavfw/n8n-nodes-eavfw" :Failed to save installed package
2025-02-21T11:32:25.060811981Z Cause: async function (requestOptions) {
2025-02-21T11:32:25.060815474Z                                 const selectedCategory = this.getNodeParamete...<omitted>... } could not be cloned.
2025-02-21T11:32:25.060818456Z ResponseError: Error loading package "@eavfw/n8n-nodes-eavfw" :Failed to save installed package
2025-02-21T11:32:25.060821031Z Cause: async function (requestOptions) {
2025-02-21T11:32:25.060823346Z                                 const selectedCategory = this.getNodeParamete...<omitted>... } could not be cloned.
2025-02-21T11:32:25.060825848Z     at CommunityPackagesController.installPackage (/usr/local/lib/node_modules/n8n/dist/controllers/community-packages.controller.js:81:19)
2025-02-21T11:32:25.060828325Z     at handler (/usr/local/lib/node_modules/n8n/dist/decorators/controller.registry.js:93:24)
2025-02-21T11:32:25.060830734Z     at /usr/local/lib/node_modules/n8n/dist/response-helper.js:110:26
2025-02-21T11:32:25.060833077Z 

Hi.
Maybe you can remove it in Terminal of your own server.

Installing custom nodes runs npm install command internally.
So you can uninstall with npm remove <custom-node-name>

Hope this would be helpful.

If you have any further questions, please ping me via WhatsApp
+1 718 207 2749

Thank you.

I have now cleaned it up, and also cleaned up the database.

I started all over with template node.

EAVFW/n8n-nodes-eav

it is on npm (n8n-nodes-eav) and i still get the exact same error.

I did also inpect the code for n8n source on github and the fact that it shows up in the db seems that its the last stage of installing that fails.

i still think its something in n8n that has bugged- atleast the sampel node repostiory does not work for me.

if i just upload the dist folder to custom folder on n8n (similar to how i test locally) then they work. Its the install process that does not work atm

hello! I’m having exactly the same issue. Trying to rollback a few versions to see if I can fix it. I’m using Docker.

same problem here.Did you manage to uninstall the broken package? tks

I ended up pulling out the sqlite db and cleaning the two tables installedpackages and installednodes

but it did not solve my problem as i still got the clone issue.

I then made a new instance on my coolify machine with just the docker image and not the “package” they offer and it all loked good, i tried to migrate the sql but then alot of credencials broke and i ended up deleting it all together.

Then i setup a new application based on docker and it happened again when i changed the domain in coolify, so i dont know how that could be related ( i think i must have doen somethign else)

Lastly i deleted and setup again and was able to install my node (same package that broke earlier). I have not been able to find out what is wrong - i been going over source code and found that it happens in the post install steps as its correctly added to db even if it fails.

So basically right now my only working resolution was to start over with a fresh n8n - sadly. Hoping it wont come again

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