github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-11 00:04:08 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

403 OPTIONS "/api/generate" #2

New Issue
Closed
opened 2025-11-11 14:01:30 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2025-11-11 14:01:30 -06:00
Owner
Copy Link

Originally created by @Chillance on GitHub (Oct 17, 2023).

Originally assigned to: @tjbck on GitHub.

Hi!

Just tested this and noticed it does a OPTIONS "/api/generate" request. From what I can tell this doesn't exist in latest ollama code...

Thoughts?

Originally created by @Chillance on GitHub (Oct 17, 2023). Originally assigned to: @tjbck on GitHub. Hi! Just tested this and noticed it does a OPTIONS "/api/generate" request. From what I can tell this doesn't exist in latest ollama code... Thoughts?
GiteaMirror commented 2025-11-11 14:01:31 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Oct 18, 2023):

Hi there,

Browsers often send an OPTIONS request to verify CORS, which might be the case here. Were there any other issues caused by the OPTIONS request?

Thanks.

@tjbck commented on GitHub (Oct 18, 2023): Hi there, Browsers often send an OPTIONS request to verify CORS, which might be the case here. Were there any other issues caused by the OPTIONS request? Thanks.
GiteaMirror commented 2025-11-11 14:01:31 -06:00
Author
Owner
Copy Link

@Chillance commented on GitHub (Oct 18, 2023):

Well, I get that asking something trying to generate something, but it seems to stop there so nothing else happens.

@Chillance commented on GitHub (Oct 18, 2023): Well, I get that asking something trying to generate something, but it seems to stop there so nothing else happens.
GiteaMirror commented 2025-11-11 14:01:32 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Oct 18, 2023):

Could you please provide any specific error messages or logs that you encounter during the process? This information would greatly assist me in diagnosing the problem more accurately and providing you with the appropriate guidance.

Thanks.

@tjbck commented on GitHub (Oct 18, 2023): Could you please provide any specific error messages or logs that you encounter during the process? This information would greatly assist me in diagnosing the problem more accurately and providing you with the appropriate guidance. Thanks.
GiteaMirror commented 2025-11-11 14:01:32 -06:00
Author
Owner
Copy Link

@Chillance commented on GitHub (Oct 19, 2023):

How do I get better logs? I tried typing something, pressed enter, and then nothing.

@Chillance commented on GitHub (Oct 19, 2023): How do I get better logs? I tried typing something, pressed enter, and then nothing.
GiteaMirror commented 2025-11-11 14:01:32 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Oct 19, 2023):

Hi there,

To obtain more detailed logs, you can use the following command for Docker:

docker logs ollama-webui

Additionally, it would be helpful for diagnosing your issue if you could provide a screenshot of your console logs from your browser's developer tools. This will allow us to examine any client-side errors or issues that might not be visible in the server logs.

Please feel free to share the Docker logs and the browser console logs screenshot, and we'll do our best to assist you in resolving the problem.

Thanks.

@tjbck commented on GitHub (Oct 19, 2023): Hi there, To obtain more detailed logs, you can use the following command for Docker: ```bash docker logs ollama-webui ``` Additionally, it would be helpful for diagnosing your issue if you could provide a screenshot of your console logs from your browser's developer tools. This will allow us to examine any client-side errors or issues that might not be visible in the server logs. Please feel free to share the Docker logs and the browser console logs screenshot, and we'll do our best to assist you in resolving the problem. Thanks.
GiteaMirror commented 2025-11-11 14:01:32 -06:00
Author
Owner
Copy Link

@coolaj86 commented on GitHub (Oct 21, 2023):

@Chillance Part of the reason that browsers invented CORS Preflight Requests (the OPTIONS issue) is to prevent people from stumbling into security issues.

Do you already have the access protected with an API token or HTTP Basic Auth?

Check out https://github.com/jmorganca/ollama/issues/849#issuecomment-1773697189 and the CORS section at https://webinstall.dev/caddy.

@coolaj86 commented on GitHub (Oct 21, 2023): @Chillance Part of the reason that browsers invented CORS Preflight Requests (the OPTIONS issue) is to prevent people from stumbling into security issues. Do you already have the access protected with an API token or HTTP Basic Auth? Check out https://github.com/jmorganca/ollama/issues/849#issuecomment-1773697189 and the CORS section at https://webinstall.dev/caddy.
GiteaMirror commented 2025-11-11 14:01:33 -06:00
Author
Owner
Copy Link

@coolaj86 commented on GitHub (Oct 21, 2023):

Tested, Working Example

See #10

@coolaj86 commented on GitHub (Oct 21, 2023): # Tested, Working Example See #10
GiteaMirror commented 2025-11-11 14:01:33 -06:00
Author
Owner
Copy Link

@Chillance commented on GitHub (Oct 22, 2023):

I don't do anything particular but just staring the ollama serve. And, on the same machine I run this in docker.

docker run --network=host -p 3000:3000 --name ollama-webui --restart always ollama-webui

I actually got chatbot-ollama (other repo) working fine. But here I can see this in the console log:

e87e0c1f-4d67-4015-959a-0e2b59659483
2.fb1b6367.js:52 submitPrompt
192.168.1.11/:1 Access to fetch at 'http://192.168.1.11:11434/api/generate' from origin 'http://192.168.1.11:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
start.93b882e2.js:1

   POST http://192.168.1.11:11434/api/generate net::ERR_FAILED

window.fetch @ start.93b882e2.js:1
R @ 2.fb1b6367.js:52
await in R (async)
re @ 2.fb1b6367.js:58
start.93b882e2.js:1

   Uncaught (in promise) TypeError: Failed to fetch
at window.fetch (start.93b882e2.js:1:1402)
at R (2.fb1b6367.js:52:108120)
@Chillance commented on GitHub (Oct 22, 2023): I don't do anything particular but just staring the ollama serve. And, on the same machine I run this in docker. `docker run --network=host -p 3000:3000 --name ollama-webui --restart always ollama-webui` I actually got chatbot-ollama (other repo) working fine. But here I can see this in the console log: > > e87e0c1f-4d67-4015-959a-0e2b59659483 > 2.fb1b6367.js:52 submitPrompt > 192.168.1.11/:1 Access to fetch at 'http://192.168.1.11:11434/api/generate' from origin 'http://192.168.1.11:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. > start.93b882e2.js:1 > > POST http://192.168.1.11:11434/api/generate net::ERR_FAILED > window.fetch @ start.93b882e2.js:1 > R @ 2.fb1b6367.js:52 > await in R (async) > re @ 2.fb1b6367.js:58 > start.93b882e2.js:1 > > Uncaught (in promise) TypeError: Failed to fetch > at window.fetch (start.93b882e2.js:1:1402) > at R (2.fb1b6367.js:52:108120)
GiteaMirror commented 2025-11-11 14:01:33 -06:00
Author
Owner
Copy Link

@Chillance commented on GitHub (Oct 22, 2023):

And
docker logs ollama-webui
only returns:
Listening on 0.0.0.0:3000

@Chillance commented on GitHub (Oct 22, 2023): And `docker logs ollama-webui` only returns: `Listening on 0.0.0.0:3000`
GiteaMirror commented 2025-11-11 14:01:33 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Oct 22, 2023):

Your logs confirm the CORS error as expected, you should pull the latest commit of the main branch and build the docker container. It introduces breaking changes so your command should be replaced with the following instead:

docker build --build-arg OLLAMA_API_BASE_URL='' -t ollama-webui .
docker run -d -p 3000:8080 --name ollama-webui --restart always ollama-webui

Also make sure to run the following command to serve Ollama, as mentioned here, which should solve your issue:

OLLAMA_HOST=0.0.0.0 OLLAMA_ORIGINS=* ollama serve

Thanks.

@tjbck commented on GitHub (Oct 22, 2023): Your logs confirm the CORS error as expected, you should pull the latest commit of the main branch and build the docker container. It introduces breaking changes so your command should be replaced with the following instead: ```sh docker build --build-arg OLLAMA_API_BASE_URL='' -t ollama-webui . docker run -d -p 3000:8080 --name ollama-webui --restart always ollama-webui ``` Also make sure to run the following command to serve Ollama, as mentioned [here](https://github.com/ollama-webui/ollama-webui#accessing-ollama-web-interface-over-lan), which should solve your issue: ```sh OLLAMA_HOST=0.0.0.0 OLLAMA_ORIGINS=* ollama serve ``` Thanks.
GiteaMirror commented 2025-11-11 14:01:34 -06:00
Author
Owner
Copy Link

@Chillance commented on GitHub (Oct 25, 2023):

Thanks! Works now!

@Chillance commented on GitHub (Oct 25, 2023): Thanks! Works now!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?