Cohere reranker returns 403

Questions
,
1

Describe the problem/error/question

I am currently working on RAG-pipeline for my AI-agent, using Qdrant vector store and Cohere for reranking chunks. Everything worked well until Cohere reranker started returning 403-error. I do not understand: is this an api-usage issue or data which stored in my Qsrant vector store issue?

Error output:
ForbiddenError Status code: 403 Body: { "ok": false, "error": { "reason": "non-json", "statusCode": 403, "rawBody": "<!doctype html><meta charset=\"utf-8\"><meta name=viewport content=\"width=device-width, initial-scale=1\"><title>403</title>403 Forbidden" } }

But when I check this API-key on Cohere website, it works well:

image
image1900×756 155 KB

Details: my n8n is self-hosted on VPS, using Docker.

What is the error message (if any)?

Error output:
ForbiddenError Status code: 403 Body: { "ok": false, "error": { "reason": "non-json", "statusCode": 403, "rawBody": "<!doctype html><meta charset=\"utf-8\"><meta name=viewport content=\"width=device-width, initial-scale=1\"><title>403</title>403 Forbidden" } }

image
image1141×433 40.5 KB

**

Error occurs when I try to enter api-token in "Credential" page:**

image
image989×405 16.1 KB

Couldn’t connect with these settings

Forbidden - perhaps check your credentials?

Please share your workflow

Share the output returned by the last node

ForbiddenError Status code: 403 Body: { “ok”: false, “error”: { “reason”: “non-json”, “statusCode”: 403, “rawBody”: “403403 Forbidden” } }

Information on your n8n setup

  • n8n version: 1.120.3
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Linux
2

The 403 Forbidden error from the Cohere Reranker node usually indicates an issue with your API key or the request itself. Since your API key works on the Cohere website, the problem is likely within your n8n workflow.

You should double-check the Cohere API key in your Reranker node configuration to ensure it’s entered correctly and hasn’t expired. Also, examine the input data being sent to the Reranker node, as incorrect formatting can sometimes trigger a 403 error.

If the key and data look correct, try restarting your n8n instance.