Hi everyone, I can’t update any of my community nodes. I found this topic but the problem doesn’t seem to be the same: nothing really happens when clicking the update button, and even after reloading my docker n8n container, the version of the community node is still the same. I deactivated all my workflows before trying to update the node. I wanted to try to uninstall it and then reinstall it but:
I’m really afraid of deleting every block linked to this node in my workflows
I can’t anyway as trying to uninstall one of my community nodes leads to the same error
Describe the problem/error/question
When trying to update any of the installed community nodes (currently n8n-nodes-imap, n8n-nodes-seaadmin and n8n-nodes-seatable) or to uninstall one of them, nothing happens.
What is the error message (if any)?
I get this error message in the JS console of the browser : TypeError: this.activePackage is undefined (from vendor-CqkvC5oQ.js:1937:13).
Information on your n8n setup
my n8n setup
n8n version: 1.50.1
Database (default: SQLite): PostgreSQL
n8n EXECUTIONS_PROCESS setting (default: own, main): sorry I didn’t manage to find this piece of info
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
Hi @bennhatton Thanks for posting and sorry to hear about your issues.
When trying to update any of the installed community nodes (currently n8n-nodes-imap , n8n-nodes-seaadmin and n8n-nodes-seatable ) or to uninstall one of them, nothing happens.
When you say ‘nothing happens’, what do you mean exactly?
Have you tried clearing your browser cache? Or adding a new updated node on the canvas, and transferring the settings instead of reusing the existing ones?
Hi @aya ,
Sorry, I think I wasn’t precise enough: I’m not talking about anything happening in a canvas, but on the settings/community nodes page.
As you can see on this gif : literally nothing happens (except for the error message popping in the console)
I tried to clear my browser cache but it doesn’t change anything…
Downgrading is generally an option in cases like these, but I think there are some DB migrations in the recent release, so my recommendation would be either to wait a few days (since we are prioritizing fixing this ASAP), or you try going to the /home/node/.n8n/nodes folder inside the n8n container, and try running npm install [[PACKAGE_NAME]]@latest.
My personal recommendation would be to wait for the patch release that’ll hopefully go out before EOD tomorrow.
Thanks for posting and sorry to hear about your issues.
