github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-08-22 16:44:06 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #3489] /ollama/v1/chat/completions endpoint broke (405 Method Not Allowed) in v0.3.6 #28812

New Issue
Closed
opened 2026-04-25 03:21:33 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-25 03:21:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @kobaltz on GitHub (Jun 28, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/3489

Bug Report

Description

Bug Summary:
Making a HTTP POST to /ollama/v1/chat/completions worked in v0.3.5 but now returns 405 - Method not allowed

Steps to Reproduce:
Using the docker compose file which at the time was referencing v0.3.6, I was unable to make API calls to the Chat Completion
Reverting the open webui image to v0.3.5 and the POST works as expected.

services:
  ollama:
    volumes:
      - ollama:/root/.ollama
    container_name: ollama
    pull_policy: always
    tty: true
    restart: unless-stopped
    image: ollama/ollama:${OLLAMA_DOCKER_TAG-latest}
    environment:
      - NVIDIA_VISIBLE_DEVICES=all
      - NVIDIA_DRIVER_CAPABILITIES=all
    deploy:
      resources:
        reservations:
          devices:
            - capabilities: [gpu]
  open-webui:
    build:
      context: .
      args:
        OLLAMA_BASE_URL: '/ollama'
      dockerfile: Dockerfile
    image: ghcr.io/open-webui/open-webui:${WEBUI_DOCKER_TAG-main}
    container_name: open-webui
    volumes:
      - open-webui:/app/backend/data
    depends_on:
      - ollama
    ports:
      - ${OPEN_WEBUI_PORT-2039}:8080
    environment:
      - 'OLLAMA_BASE_URL=http://ollama:11434'
    extra_hosts:
      - host.docker.internal:host-gateway
    restart: unless-stopped

volumes:
  ollama: {}
  open-webui: {}

Expected Behavior:
HTTP POST to /ollama/v1/chat/completions returns the JSON response

Actual Behavior:
405 Method Not Allowed when making HTTP POST to /ollama/v1/chat/completions

Environment

  • Open WebUI Version: main (and v0.3.6)

  • Ollama (if applicable): latest (and 0.1.47)

  • Operating System: Debian Bookworm

  • Browser (if applicable): n/a

Reproduction Details

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on the latest version of both Open WebUI and Ollama.
  • I have included the Docker container logs.

Logs and Screenshots

Docker Container Logs:

INFO:apps.ollama.main:url: http://ollama:11434
INFO:     my-ip:0 - "POST /ollama/v1/chat/completions HTTP/1.1" 405 Method Not Allowed
INFO:apps.ollama.main:url: http://ollama:11434
INFO:     my-ip:0 - "POST /ollama/v1/chat/completions HTTP/1.1" 405 Method Not Allowed

Installation Method

Docker Compose

Originally created by @kobaltz on GitHub (Jun 28, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/3489 # Bug Report ## Description **Bug Summary:** Making a HTTP POST to /ollama/v1/chat/completions worked in v0.3.5 but now returns 405 - Method not allowed **Steps to Reproduce:** Using the docker compose file which at the time was referencing v0.3.6, I was unable to make API calls to the Chat Completion Reverting the open webui image to v0.3.5 and the POST works as expected. ``` services: ollama: volumes: - ollama:/root/.ollama container_name: ollama pull_policy: always tty: true restart: unless-stopped image: ollama/ollama:${OLLAMA_DOCKER_TAG-latest} environment: - NVIDIA_VISIBLE_DEVICES=all - NVIDIA_DRIVER_CAPABILITIES=all deploy: resources: reservations: devices: - capabilities: [gpu] open-webui: build: context: . args: OLLAMA_BASE_URL: '/ollama' dockerfile: Dockerfile image: ghcr.io/open-webui/open-webui:${WEBUI_DOCKER_TAG-main} container_name: open-webui volumes: - open-webui:/app/backend/data depends_on: - ollama ports: - ${OPEN_WEBUI_PORT-2039}:8080 environment: - 'OLLAMA_BASE_URL=http://ollama:11434' extra_hosts: - host.docker.internal:host-gateway restart: unless-stopped volumes: ollama: {} open-webui: {} ``` **Expected Behavior:** HTTP POST to /ollama/v1/chat/completions returns the JSON response **Actual Behavior:** 405 Method Not Allowed when making HTTP POST to /ollama/v1/chat/completions ## Environment - **Open WebUI Version:** main (and v0.3.6) - **Ollama (if applicable):** latest (and 0.1.47) - **Operating System:** Debian Bookworm - **Browser (if applicable):** n/a ## Reproduction Details **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on the latest version of both Open WebUI and Ollama. - [x] I have included the Docker container logs. ## Logs and Screenshots **Docker Container Logs:** ``` INFO:apps.ollama.main:url: http://ollama:11434 INFO: my-ip:0 - "POST /ollama/v1/chat/completions HTTP/1.1" 405 Method Not Allowed INFO:apps.ollama.main:url: http://ollama:11434 INFO: my-ip:0 - "POST /ollama/v1/chat/completions HTTP/1.1" 405 Method Not Allowed ``` ## Installation Method Docker Compose
GiteaMirror commented 2026-04-25 03:21:35 -05:00
Author
Owner
Copy Link
Copy Source

@debemdeboas commented on GitHub (Jun 28, 2024):

Seeing this here as well.
Also seeing a TypeError: signup() missing 1 required positional argument: 'form_data'.
Going back to v0.3.5 fixes things.

<!-- gh-comment-id:2196876614 --> @debemdeboas commented on GitHub (Jun 28, 2024): Seeing this here as well. Also seeing a `TypeError: signup() missing 1 required positional argument: 'form_data'`. Going back to v0.3.5 fixes things.
GiteaMirror commented 2026-04-25 03:21:35 -05:00
Author
Owner
Copy Link
Copy Source

@justinh-rahb commented on GitHub (Jun 28, 2024):

Can you share the exact cURL command you've used to test, as well as additional browser dev console logs, maybe some more backend logs as well to help us out.

<!-- gh-comment-id:2197095765 --> @justinh-rahb commented on GitHub (Jun 28, 2024): Can you share the exact cURL command you've used to test, as well as additional browser dev console logs, maybe some more backend logs as well to help us out.
GiteaMirror commented 2026-04-25 03:21:36 -05:00
Author
Owner
Copy Link
Copy Source

@kobaltz commented on GitHub (Jun 28, 2024):

Here's the cURL command.

curl -X POST \
  http://127.0.0.1:2039/ollama/v1/chat/completions \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer sk-89ddf4d66bae4527974150ee796e71f6' \
  -d '{
       "model": "llama3:instruct",
       "messages": [
         {
           "role": "user",
           "content": "Tell me a story"
         }
       ],
       "max_tokens": 50
     }'
     
=> {"detail":"Method Not Allowed"}

But, if I change the docker compose file to v0.3.5 and run the same command, I get

=> {"id":"chatcmpl-138","object":"chat.completion","created":1719588557,"model":"llama3:instruct","system_fingerprint":"fp_ollama","choices":[{"index":0,"message":{"role":"assistant","content":"Once upon a time, in a small village nestled in the rolling hills of Tuscany, there was a little girl named Sophia. She lived with her family in a charming stone house with a bright red door and a garden full of fragrant herbs"},"finish_reason":"length"}],"usage":{"prompt_tokens":0,"completion_tokens":50,"total_tokens":50}}

Since I'm using just the cURL command, there isn't any additional logs as the docker container logas are just saying that the method isn't allowed. Maybe there is a debug ENV var I could add to get a more verbose output?

<!-- gh-comment-id:2197183517 --> @kobaltz commented on GitHub (Jun 28, 2024): Here's the cURL command. ``` curl -X POST \ http://127.0.0.1:2039/ollama/v1/chat/completions \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer sk-89ddf4d66bae4527974150ee796e71f6' \ -d '{ "model": "llama3:instruct", "messages": [ { "role": "user", "content": "Tell me a story" } ], "max_tokens": 50 }' => {"detail":"Method Not Allowed"} ``` But, if I change the docker compose file to `v0.3.5` and run the same command, I get ``` => {"id":"chatcmpl-138","object":"chat.completion","created":1719588557,"model":"llama3:instruct","system_fingerprint":"fp_ollama","choices":[{"index":0,"message":{"role":"assistant","content":"Once upon a time, in a small village nestled in the rolling hills of Tuscany, there was a little girl named Sophia. She lived with her family in a charming stone house with a bright red door and a garden full of fragrant herbs"},"finish_reason":"length"}],"usage":{"prompt_tokens":0,"completion_tokens":50,"total_tokens":50}} ``` Since I'm using just the cURL command, there isn't any additional logs as the docker container logas are just saying that the method isn't allowed. Maybe there is a debug ENV var I could add to get a more verbose output?
GiteaMirror commented 2026-04-25 03:21:36 -05:00
Author
Owner
Copy Link
Copy Source

@abishekmuthian commented on GitHub (Jun 29, 2024):

I'm getting Method Not Allowed for deepseek-coder-v2:latest model in v0.3.6. Other models work fine.

INFO: 127.0.0.1:41212 - "POST /ollama/api/chat HTTP/1.1" 405 Method Not Allowed

<!-- gh-comment-id:2198074747 --> @abishekmuthian commented on GitHub (Jun 29, 2024): I'm getting `Method Not Allowed` for `deepseek-coder-v2:latest ` model in v0.3.6. Other models work fine. `INFO: 127.0.0.1:41212 - "POST /ollama/api/chat HTTP/1.1" 405 Method Not Allowed`
GiteaMirror commented 2026-04-25 03:21:37 -05:00
Author
Owner
Copy Link
Copy Source

@oleksii-davydchuk commented on GitHub (Jun 29, 2024):

I'm getting Method Not Allowed for any models in v0.3.6
I used local k8s cluster, which was created with kind I got Server connection verified for the Ollama API url ollama.ollama.svc.cluster.local:11434

INFO:apps.ollama.main:app.state.config.OLLAMA_BASE_URLS: ['http://ollama.ollama.svc.cluster.local:11434']
INFO:     127.0.0.1:56508 - "POST /ollama/urls/update HTTP/1.1" 200 OK
INFO:apps.ollama.main:get_all_models()
INFO:apps.ollama.main:get_all_models()
INFO:apps.ollama.main:get_all_models()
INFO:apps.openai.main:get_all_models()
INFO:     127.0.0.1:56508 - "POST /openai/keys/update HTTP/1.1" 200 OK
INFO:     127.0.0.1:56494 - "GET /ollama/api/version HTTP/1.1" 200 OK
INFO:apps.ollama.main:get_all_models()
INFO:apps.ollama.main:get_all_models()
INFO:     127.0.0.1:56508 - "GET /api/models HTTP/1.1" 200 OK
INFO:apps.ollama.main:get_all_models()
INFO:apps.ollama.main:get_all_models()
INFO:     127.0.0.1:56494 - "GET /api/models HTTP/1.1" 200 OK
INFO:apps.ollama.main:get_all_models()
INFO:apps.ollama.main:get_all_models()
INFO:apps.ollama.main:get_all_models()
INFO:     127.0.0.1:56546 - "GET /ollama/api/version HTTP/1.1" 200 OK
INFO:     127.0.0.1:56552 - "GET /api/v1/users/user/settings HTTP/1.1" 200 OK
INFO:apps.ollama.main:get_all_models()
INFO:     127.0.0.1:56562 - "GET /api/v1/users/user/settings HTTP/1.1" 200 OK
INFO:apps.ollama.main:get_all_models()
INFO:apps.ollama.main:get_all_models()
INFO:apps.ollama.main:url: http://ollama.ollama.svc.cluster.local:11434
INFO:     127.0.0.1:52376 - "POST /ollama/api/pull/0 HTTP/1.1" 200 OK
INFO:apps.ollama.main:get_all_models()
INFO:apps.ollama.main:get_all_models()
INFO:     127.0.0.1:52376 - "GET /api/models HTTP/1.1" 200 OK
INFO:     127.0.0.1:57818 - "POST /api/v1/chats/new HTTP/1.1" 200 OK
INFO:     127.0.0.1:57818 - "GET /api/v1/chats/ HTTP/1.1" 200 OK
INFO:apps.ollama.main:url: http://ollama.ollama.svc.cluster.local:11434
INFO:     127.0.0.1:57818 - "POST /ollama/api/chat HTTP/1.1" 405 Method Not Allowed
ERROR:asyncio:Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0xfffe9473a910>
INFO:     127.0.0.1:57818 - "GET /api/v1/chats/ HTTP/1.1" 200 OK
<!-- gh-comment-id:2198286764 --> @oleksii-davydchuk commented on GitHub (Jun 29, 2024): I'm getting `Method Not Allowed` for any models in v0.3.6 I used local k8s cluster, which was created with [kind](https://kind.sigs.k8s.io/) I got `Server connection verified ` for the Ollama API url `ollama.ollama.svc.cluster.local:11434` ``` INFO:apps.ollama.main:app.state.config.OLLAMA_BASE_URLS: ['http://ollama.ollama.svc.cluster.local:11434'] INFO: 127.0.0.1:56508 - "POST /ollama/urls/update HTTP/1.1" 200 OK INFO:apps.ollama.main:get_all_models() INFO:apps.ollama.main:get_all_models() INFO:apps.ollama.main:get_all_models() INFO:apps.openai.main:get_all_models() INFO: 127.0.0.1:56508 - "POST /openai/keys/update HTTP/1.1" 200 OK INFO: 127.0.0.1:56494 - "GET /ollama/api/version HTTP/1.1" 200 OK INFO:apps.ollama.main:get_all_models() INFO:apps.ollama.main:get_all_models() INFO: 127.0.0.1:56508 - "GET /api/models HTTP/1.1" 200 OK INFO:apps.ollama.main:get_all_models() INFO:apps.ollama.main:get_all_models() INFO: 127.0.0.1:56494 - "GET /api/models HTTP/1.1" 200 OK INFO:apps.ollama.main:get_all_models() INFO:apps.ollama.main:get_all_models() INFO:apps.ollama.main:get_all_models() INFO: 127.0.0.1:56546 - "GET /ollama/api/version HTTP/1.1" 200 OK INFO: 127.0.0.1:56552 - "GET /api/v1/users/user/settings HTTP/1.1" 200 OK INFO:apps.ollama.main:get_all_models() INFO: 127.0.0.1:56562 - "GET /api/v1/users/user/settings HTTP/1.1" 200 OK INFO:apps.ollama.main:get_all_models() INFO:apps.ollama.main:get_all_models() INFO:apps.ollama.main:url: http://ollama.ollama.svc.cluster.local:11434 INFO: 127.0.0.1:52376 - "POST /ollama/api/pull/0 HTTP/1.1" 200 OK INFO:apps.ollama.main:get_all_models() INFO:apps.ollama.main:get_all_models() INFO: 127.0.0.1:52376 - "GET /api/models HTTP/1.1" 200 OK INFO: 127.0.0.1:57818 - "POST /api/v1/chats/new HTTP/1.1" 200 OK INFO: 127.0.0.1:57818 - "GET /api/v1/chats/ HTTP/1.1" 200 OK INFO:apps.ollama.main:url: http://ollama.ollama.svc.cluster.local:11434 INFO: 127.0.0.1:57818 - "POST /ollama/api/chat HTTP/1.1" 405 Method Not Allowed ERROR:asyncio:Unclosed client session client_session: <aiohttp.client.ClientSession object at 0xfffe9473a910> INFO: 127.0.0.1:57818 - "GET /api/v1/chats/ HTTP/1.1" 200 OK ```
GiteaMirror commented 2026-04-25 03:21:37 -05:00
Author
Owner
Copy Link
Copy Source

@oleksii-davydchuk commented on GitHub (Jun 29, 2024):

Issue was resolved - there was a memory shortage and the OOM kicked in.

<!-- gh-comment-id:2198328167 --> @oleksii-davydchuk commented on GitHub (Jun 29, 2024): Issue was resolved - there was a memory shortage and the OOM kicked in.
GiteaMirror commented 2026-04-25 03:21:38 -05:00
Author
Owner
Copy Link
Copy Source

@tjbck commented on GitHub (Jun 29, 2024):

Fixed on dev, 0.3.7 coming soon!

<!-- gh-comment-id:2198328727 --> @tjbck commented on GitHub (Jun 29, 2024): Fixed on dev, 0.3.7 coming soon!
GiteaMirror commented 2026-04-25 03:21:39 -05:00
Author
Owner
Copy Link
Copy Source

@Lanhild commented on GitHub (Sep 4, 2024):

Commenting about this, I am getting an error 500 with the completions endpoint:

Updating ollama to 0.3.9 fixed this.

<!-- gh-comment-id:2329414095 --> @Lanhild commented on GitHub (Sep 4, 2024): Commenting about this, I am getting an error `500` with the completions endpoint: Updating ollama to `0.3.9` fixed this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#28812