Every time I restart n8n container, the n8n-nodes-netsuite becomes unrecognized.
The error is:
The following error occurred on workflow activation:
Unrecognized node type: n8n-nodes-netsuite.n8n-nodes-netsuite.netsuite".
I am not sure if this is n8n or the node issue. I also posted on the n8n-nodes-netsuite github issue but no response from author.
n8n version: 1.54.4
Database: Postgresql
Running n8n via Docker
OS: Ubuntu 24.04
Any help would be greatly appreciated.
It looks like your topic is missing some important information. Could you provide the following if applicable.
Hey @ianpogi5,
Welcome to the community 
We don’t directly support community nodes but I can take a quick look. Which version of the node are you using and did you install it from the UI or with a custom docker image?
I am using version 0.7.6 of n8n-nodes-netsuite. I used the n8n UI to install. Thanks @Jon for your help!
here’s my docker-compose.yml
###############################################################
# Services
###############################################################
services:
n8n:
image: docker.n8n.io/n8nio/n8n:1.54.4
container_name: n8n
restart: unless-stopped
networks:
- n8n
ports:
- 5678:5678
volumes:
- n8n_data:/home/node/.n8n
environment:
DB_TYPE: postgresdb
DB_POSTGRESDB_DATABASE: n8n
DB_POSTGRESDB_HOST: postgresql
DB_POSTGRESDB_PORT: 5432
DB_POSTGRESDB_USER: xxx
DB_POSTGRESDB_PASSWORD: xxxxxx
NODE_FUNCTION_ALLOW_EXTERNAL: uuid
N8N_PROXY_HOPS: 1
WEBHOOK_URL: https://xxx.xxx.xxx
###############################################################
# Networks
###############################################################
networks:
postgresql_postgres:
external: true
n8n:
volumes:
n8n_data:
driver: local
That all looks ok. I will test the netsuite node to see if the issue is specific to that node.
Hi @Jon I did some testing and it seems that if the db is SQLite(remove all DB_ from above docker compose), everything works fine. Restarting the container does not cause n8n-nodes-netsuite to become unrecognized.
If I use posgresql as db, the error happens everytime I restart the container. Seems like an n8n issue.
@Jon I did more investigation and compared data in sqlite and postgresql. Below is the table installed_nodes.
| name | type | latestVersion | package |
|---|---|---|---|
| NetSuite | n8n-nodes-netsuite.netsuite | 1 | n8n-nodes-netsuite |
| name | type | latestVersion | package |
|---|---|---|---|
| NetSuite | n8n-nodes-netsuite.n8n-nodes-netsuite.netsuite | 1 | n8n-nodes-netsuite |
The value in column type are different in the two databases. I hope this helps in troubleshooting.
Let me know if you need more info.
The root cause of this issue was that I installed n8n-nodes-netsuite twice(install-uninstall-install) which has caused the type value to be n8n-nodes-netsuite.n8n-nodes-netsuite.netsuite. Then I created my workflows which now contain the type n8n-nodes-netsuite.n8n-nodes-netsuite.netsuite. Every time n8n restarts, my n8n-nodes-netsuite and the workflows that contain that node become unrecognized.
The solution that I did was to edit directly in the database all type with value n8n-nodes-netsuite.n8n-nodes-netsuite.netsuite and change it to n8n-nodes-netsuite.netsuite.
I still don’t know if it’s an n8n or n8n-nodes-netsuite bug that causes the incorrect type. This issue can be easily replicated using the above steps.
@ianpogi5 I think what you are looking for is this Deployment environment variables | n8n Docs
I had the same issue when runnin n8n on railkway
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
New version [email protected] got released which includes the GitHub PR 11329.
