n8n - 💡(How to fix) Fix Problem in node ‘Basic LLM Chain‘ Authorization failed - please check your credentials on OpenRouter [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28349Fetched 2026-04-11 06:30:45
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
closed ×1commented ×1cross-referenced ×1labeled ×1

Error Message

Currently I use n8n 2.15.0 and I have an issue with OpenRouter : I set the key, it's correct but when I launch the node I have an error: I see this error:

RAW_BUFFERClick to expand / collapse

Bug Description

Hi, Currently I use n8n 2.15.0 and I have an issue with OpenRouter : I set the key, it's correct but when I launch the node I have an error:

Problem in node ‘Basic LLM Chain‘ Authorization failed - please check your credentials

I see this error:

{ "errorMessage": "Authorization failed - please check your credentials", "errorDescription": "User not found.", "errorDetails": { "rawErrorMessage": [ "401 User not found.\n\nTroubleshooting URL: https://docs.langchain.com/oss/javascript/langchain/errors/MODEL_AUTHENTICATION/\n" ] }, "n8nDetails": { "nodeName": "Basic LLM Chain", "nodeType": "@n8n/n8n-nodes-langchain.chainLlm", "nodeVersion": 1.9, "time": "10/04/2026 20:36:08", "n8nVersion": "2.15.0 (Self Hosted)", "binaryDataMode": "filesystem", "stackTrace": [ "NodeOperationError: Authorization failed - please check your credentials", " at /home/clients/domain/sites/website/node_modules/@n8n/n8n-nodes-langchain/nodes/chains/ChainLLM/ChainLlm.node.ts:116:13", " at Array.forEach (<anonymous>)", " at ExecuteContext.execute (/home/clients/domain/sites/website/node_modules/@n8n/n8n-nodes-langchain/nodes/chains/ChainLLM/ChainLlm.node.ts:94:18)", " at processTicksAndRejections (node:internal/process/task_queues:105:5)", " at WorkflowExecute.executeNode (/home/clients/domain/sites/website/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1045:8)", " at WorkflowExecute.runNode (/home/clients/domain/sites/website/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1224:11)", " at /home/clients/domain/sites/website/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1670:27", " at /home/clients/domain/sites/website/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2315:11" ] } }

To Reproduce

<img width="807" height="466" alt="Image" src="https://github.com/user-attachments/assets/1bc25a2b-e287-4560-ac7b-7932f3b37226" />

Expected behavior

Launch the model on openrouter

Debug Info

See the bug description

Operating System

Debian GNU/Linux 11 (bullseye)

n8n Version

2.15.0

Node.js Version

v24.9.0

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

extent analysis

TL;DR

The issue is likely due to incorrect or missing credentials for the OpenRouter node, and verifying the key and credentials setup is the first step towards resolving the issue.

Guidance

  • Check the key setup in the OpenRouter node to ensure it matches the expected format and value.
  • Verify that the credentials are correctly configured and passed to the node, as the error message suggests an authentication issue.
  • Review the troubleshooting URL provided in the error message (https://docs.langchain.com/oss/javascript/langchain/errors/MODEL_AUTHENTICATION/) for additional guidance on resolving authentication errors with LangChain.
  • Ensure that the user account associated with the key exists and is active, as the error message indicates a "User not found" issue.

Notes

The issue seems to be related to authentication with the OpenRouter node, but without more information about the specific key and credentials being used, it's difficult to provide a more detailed solution.

Recommendation

Apply workaround: Verify and correct the credentials setup, as the error message suggests an authentication issue, and consult the provided troubleshooting URL for additional guidance.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Launch the model on openrouter

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING