I’d first check the n8n logs (docker logs -f ) right after attempting the install, because that’s usually where the real error appears.
As a workaround, I’d try installing the package manually inside the container (npm install n8n-nodes-tenable-community) or switch to the latest n8n image, since some community nodes only work with newer Node/n8n versions.
Thanks for the ideas. Unfortunately, all the logs give me is:
2026-03-17T22:38:45.368Z | error | Error loading package “n8n-nodes-tenable-community” :The specified package could not be loaded
ResponseError: Error loading package “n8n-nodes-tenable-community” :The specified package could not be loaded
at CommunityPackagesController.installPackage (/usr/local/lib/node_modules/n8n/src/modules/community-packages/community-packages.controller.ts:135:10)
at handler (/usr/local/lib/node_modules/n8n/src/controller.registry.ts:110:12)
at /usr/local/lib/node_modules/n8n/src/response-helper.ts:161:17
{“file”:“error-reporter.js”,“function”:“defaultReport”}
So it looks like its a manual install. Sorry, but I’ve never done this before, where/how “inside” the container do you mean. n8n is running using docker compose. I’m already running 2.11.4 which is the latest GA release
Hi @rossw Welcome!
You can try manually installing the node into docker instance by executing these set of commands:
# Access the container shell
docker exec -it n8n sh
# Create the nodes directory if it doesn't exist, then navigate into it
mkdir ~/.n8n/nodes
cd ~/.n8n/nodes
# Install the package
npm i n8n-nodes-some-node-package
and then just restart your container that should work, also make sure that community node is being perfectly installed in other instances as well as there are some cases where nodes are not configured correctly.
Hi there, thanks for the response.
I have managed to get further along, but….
I installed the community node as you suggested, and it installed the node and a bunch of dependencies - ok.
If I look in the nodes folder I can see that the package.json file has been updated with the correct info, and there is now a package-lock.json as well.
When I look in the GUI under settings→community nodes, it does not appear, but the imap node I installed to test the whole concept of installing a community node does appear.
When I go to create a flow, I can find the imap node, with the little box icon so that looks right, but I cannot find the tenable node there at all.
In the .env file, I have added N8N_REINSTALL_MISSING_PACKAGES=true and N8N_COMMUNITY_PACKAGES_ENABLED=true.
Any other hints??
@rossw As other community nodes you are installing are working fine except the tenable node i think this is a great sign that there is something wrong with that specific node not your current setup as every other node you have installed appears in the community nodes and are usable in the n8n workspace, i recommend using a HTTP node instead of community node as this clearly means there is something wrong with tenable node like usually this happens when the node class is not named correctly in the package itself, but still i would recommend try restarting the container after the manual installation.
Thanks for the help. I was able to install the alternative node without issues, leading me to believe that you are right and there are issues in the node I am trying to install. Unfortunately, the alternative node is not coded for the version of the Tenable product set I am trying to use (Security Center) and it will not work (I tried), so it looks like I’m back to the basic http node.
Thanks again for your assistance. Ross