4nk/smart_ide
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

README ia.enso: Cursor ERROR_BAD_USER_API_KEY vs proxy OK

Browse Source 
**Motivations:**
- Operators confuse nginx Bearer with Cursor user API key error.

**Root causes:**
- Cursor validates or routes chat through its backend; custom URL can still fail in-app.

**Correctifs:**
- N/A.

**Evolutions:**
- README Cursor subsection + forum link.

**Pages affectées:**
- deploy/nginx/README-ia-enso.md
This commit is contained in:
Nicolas Cantu 2026-03-23 02:05:21 +01:00
parent 86bfaa8f7c
commit dfc978deef
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
deploy/nginx/README-ia-enso.md
View File

@ -156,7 +156,9 @@ Si les assets statiques échouent, vérifier la doc upstream (sous-chemin, en-t
### Cursor ### Cursor
- URL de base OpenAI : `https://ia.enso.4nkweb.com/ollama/v1` - URL de base OpenAI : `https://ia.enso.4nkweb.com/ollama/v1`
- Clé API : **identique** au secret Bearer (sans préfixe `Bearer ` dans le champ ; Cursor envoie `Authorization: Bearer <clé>`). - Clé API : **identique** au secret Bearer du `map` nginx (sans préfixe `Bearer ` dans le champ ; Cursor envoie `Authorization: Bearer <clé>`).
Si **`curl`** vers `/ollama/v1/models` ou `/ollama/api/tags` avec ce Bearer renvoie **200** mais Cursor affiche **`ERROR_BAD_USER_API_KEY` / `Unauthorized User API key`**, l’échec vient **du client Cursor** (validation ou routage via l’infra Cursor), pas du proxy. Cas signalés sur le forum Cursor : [Unauthorized User API key with custom openai api key/url](https://forum.cursor.com/t/unauthorized-user-api-key-with-custom-openai-api-key-url/132572). Vérifier version de Cursor, mode confidentialité / type de compte, et sujets liés à l’override d’URL OpenAI.
--- ---