ollama: attaching a file does not work/results in error 500/400 Bad request

Open

#11 opened on Dec 14, 2025 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: javascript, ollama
Domain: api, backend

Research direction

Start with the OllamaProvider path used by the --serve web UI and inspect the POST request to /v1/chat/completions shown in the logs. Reproduce with a text, shell, or Python attachment and compare the file content payload with Ollama's accepted format. Done means the attached document is summarized without the provider returning HTTP 400 or the server returning HTTP 500.

Written by the indexing model from the issue text.

Description

Steps to reproduce:

llms --serve 8080 --verbose, access web UI
select ollama provider (tested with multiple models)
attach a file (tested with multiple text files/shell/python scripts) with a promt su chas Please summarize this document and submit the query
the web UI displays an error and not response is returned

HTTP 500 Internal Server Error
{
  "error": "HTTP 400 Bad Request"
}

Logs:

provider: ollama OllamaProvider
POST http://localhost:11434/v1/chat/completions
{
  "model": "deepseek-r1:14b",
  "messages": [
    {
      "role": "user",
      "content": [
        {
          "type": "file",
          "file": {
            "filename": "test.xml",
            "file_data": "data:text/xml;base64,(1325)"
          }
        },
        {
          "type": "text",
          "text": "Summarize the file\n\n[\ud83d\udcce test.xml]"
        }
      ]
    }
  ],
  "enable_thinking": true,
  "metadata": {
    "threadId": "1765739448549"
  },
  "stream": false
}
Provider ollama failed: HTTP 400 Bad Request

Dominant language: JavaScript
Stars: 629
Forks: 31
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Duplicate Code] Repeated filtered model-alias assembly in proxy server Open

code-quality refactoring

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

github/gh-aw-firewall#8816 · Opened Sep 20, 2026
quickjs: support `timeout=None` (no per-call deadline) in `CodeInterpreterMiddleware` Open

integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

langchain-ai/deepagents#6450 · Opened Sep 20, 2026
[optimization:agents-md-curator] AGENTS.md: compress duplicated Debugging & Logging section and merge redundant autopilot rules Open

optimization optimization:agents-md-curator

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

githubnext/gh-aw-cao#13143 · Opened Sep 20, 2026
[BUG] schema-compat/zodToJsonSchema: nullable zod v4 enum/literal widens to type:[X,"null"] but keeps enum/const, so exported schema rejects null Open

status: needs triage

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

mastra-ai/mastra#24516 · 2 comments · Opened Sep 20, 2026
Kubernetes request flow diagram 404s on both copies of the tutorial Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

layer5io/docs#1263 · Opened Sep 20, 2026

More JavaScript issues