Dear n8n Support Team,
I am reaching out regarding an issue with my self-hosted n8n instance (version 1.91.3) running on a Hetzner server (Ubuntu, 4GB RAM). I am unable to create a credential for the Pinecone integration, and the Pinecone node does not appear to be properly installed or available.
Here are the details of the issue:
- Problem: I cannot create a Pinecone credential in the n8n UI (accessible at https://n8n.manparnian.ir). The Pinecone option does not appear in the Credentials list, and I suspect the Pinecone node is not installed or supported in my version.
- Context: The same Pinecone API key works perfectly on the n8n cloud platform, but it fails on my self-hosted instance. When I test the API key manually using
curl(e.g.,curl -v -H "Api-Key: <my_key>" https://api.pinecone.io/indexes), I receive a 403 Forbidden error, which suggests an authentication issue or node misconfiguration. - Attempts to Resolve:
- I tried installing the Pinecone node using
docker exec n8n-docker-n8n-1 npm install @n8n/n8n-nodes-pinecone, but received a 404 error: “package not found in registry.” - I checked the n8n logs (
docker logs n8n-docker-n8n-1), which show errors like “Node does not have any credentials set” and “Request failed with status code 403” for the “Inventory Stock” workflow (ID: MSmYVmk3vcaXcqkw). - I confirmed network connectivity to Pinecone’s API (
api.pinecone.io) usingcurl -v, and the SSL handshake was successful. - My server has sufficient resources (4GB RAM, verified with
free -mandtop), and the domain (n8n.manparnian.ir) has a valid SSL certificate.
- I tried installing the Pinecone node using
- Environment:
- n8n Version: 1.91.3
- Hosting: Hetzner (Ubuntu, Docker-based)
- Workflow: “Inventory Stock” (ID: MSmYVmk3vcaXcqkw)
- Pinecone Environment: [e.g., us-west1-gcp, please specify your environment]
- Index Name: [please specify your index name]
Could you please assist with the following:
- Confirm whether the Pinecone node is supported in n8n version 1.91.3 or if I need to upgrade to a newer version.
- Provide the correct npm package name or installation method for the Pinecone node, as
@n8n/n8n-nodes-pineconewas not found. - Advise on any additional configuration needed to enable the Pinecone node and create credentials on a self-hosted instance.
- Suggest any debugging steps to resolve the 403 Forbidden error when using the Pinecone API on my server.
I would appreciate any guidance or documentation links to resolve this issue. Please let me know if you need additional details, such as specific logs, workflow configurations, or screenshots from the n8n UI.
Thank you for your support!