I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.6.18
Ollama Version (if applicable)
No response
Operating System
Rocky Linux
Browser (if applicable)
No response
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
curl -X POST http://192.168.254.42:8080/api/v1/chat/completions
-H "Content-Type: application/json"
-H "Authorization: Bearer sk-123 (real API KEY hidden)" \
-d '{
"model": "coding-assistent",
"messages": [
{
"role": "user",
"content": "Wie kann ich eine SQL-Abfrage schreiben, um alle Benutzer aus einer Datenbank zu selektieren?"
}
]
}'
{"detail":"Method Not Allowed"}%
Steps to Reproduce
Run OpenWebUI with docker in production mode
Make API accessible via the UI
Try OpenAI compatible Endpoints
Logs & Screenshots
Logs from the OpenWebUI container 2025-08-07 10:51:45.957 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 192.168.200.125:51757 - "GET /api/v1/chats/?page=2 HTTP/1.1" 200 - {}
Originally created by @jsivu on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16349
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.6.18
### Ollama Version (if applicable)
_No response_
### Operating System
Rocky Linux
### Browser (if applicable)
_No response_
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
My OpenWebUI instance is running on http://192.168.254.42:8080. For an open ai compatible endpoint the endpoint post http://192.168.254.42:8080/v1/chat/completions should return the chat completion. Generally the api works but only with curl -X POST http://192.168.254.42:8080/api/chat/completions, so without the v1. For connecting OpenWebUI with services that expect OpenAI compatible Endpoints, that's really a problem.
### Actual Behavior
That's the output for the call
curl -X POST http://192.168.254.42:8080/api/v1/chat/completions \
-H "Content-Type: application/json" \
-H "Authorization: Bearer sk-123 (real API KEY hidden)" \
-d '{
"model": "coding-assistent",
"messages": [
{
"role": "user",
"content": "Wie kann ich eine SQL-Abfrage schreiben, um alle Benutzer aus einer Datenbank zu selektieren?"
}
]
}'
{"detail":"Method Not Allowed"}%
### Steps to Reproduce
1. Run OpenWebUI with docker in production mode
2. Make API accessible via the UI
3. Try OpenAI compatible Endpoints
### Logs & Screenshots
Logs from the OpenWebUI container 2025-08-07 10:51:45.957 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 192.168.200.125:51757 - "GET /api/v1/chats/?page=2 HTTP/1.1" 200 - {}
2025-08-07 10:51:45.967 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 192.168.200.125:51757 - "GET /api/v1/folders/ HTTP/1.1" 200 - {}
2025-08-07 10:51:47.458 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 172.20.200.134:54983 - "POST /api/v1/chat/completions HTTP/1.1" 405 - {}
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-19 23:45:54 -05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jsivu on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16349
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.18
Ollama Version (if applicable)
No response
Operating System
Rocky Linux
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
My OpenWebUI instance is running on http://192.168.254.42:8080. For an open ai compatible endpoint the endpoint post http://192.168.254.42:8080/v1/chat/completions should return the chat completion. Generally the api works but only with curl -X POST http://192.168.254.42:8080/api/chat/completions, so without the v1. For connecting OpenWebUI with services that expect OpenAI compatible Endpoints, that's really a problem.
Actual Behavior
That's the output for the call
curl -X POST http://192.168.254.42:8080/api/v1/chat/completions
-H "Content-Type: application/json"
-H "Authorization: Bearer sk-123 (real API KEY hidden)" \
-d '{
"model": "coding-assistent",
"messages": [
{
"role": "user",
"content": "Wie kann ich eine SQL-Abfrage schreiben, um alle Benutzer aus einer Datenbank zu selektieren?"
}
]
}'
{"detail":"Method Not Allowed"}%
Steps to Reproduce
Logs & Screenshots
Logs from the OpenWebUI container 2025-08-07 10:51:45.957 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 192.168.200.125:51757 - "GET /api/v1/chats/?page=2 HTTP/1.1" 200 - {}
2025-08-07 10:51:45.967 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 192.168.200.125:51757 - "GET /api/v1/folders/ HTTP/1.1" 200 - {}
2025-08-07 10:51:47.458 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 172.20.200.134:54983 - "POST /api/v1/chat/completions HTTP/1.1" 405 - {}
Additional Information
No response