github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #282] CORS requests don't work when origin is 0.0.0.0 #124

New Issue
Closed
opened 2026-04-12 09:39:25 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 09:39:25 -05:00
Owner
Copy Link

Originally created by @jmorganca on GitHub (Aug 4, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/282

When connecting to localhost:11434 from a host served on 0.0.0.0, requests are blocked due to CORS checks – which are important to have, but we should consider opening them up to 0.0.0.0 as well

Originally created by @jmorganca on GitHub (Aug 4, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/282 When connecting to `localhost:11434` from a host served on `0.0.0.0`, requests are blocked due to CORS checks – which are important to have, but we should consider opening them up to `0.0.0.0` as well
GiteaMirror added the buggood first issue labels 2026-04-12 09:39:25 -05:00
GiteaMirror commented 2026-04-12 09:39:26 -05:00
Author
Owner
Copy Link

@Kylejustknows commented on GitHub (Dec 19, 2024):

OMG, running Ollama is so easy, but connect to it is so hard and require super deep advanced network/server/html knowledge.

There are tons of posts all asking the same thing.

I consider myself a pretty good old-school server manager. I spent like 2 hours tuning the env OLLAMA_ORIGINS and the caddy + HTML on a windows server, still getting the CORS. Now trying to setup a local proxy to forward the stupid thing.

If running a non-standard service (simple handmade etc.) trying to connect to Ollama, it is a nightmare!

Could Ollama just remove all the CORS restrict things, just run as a plaint service, let users handle their network port security etc please?

<!-- gh-comment-id:2552517733 --> @Kylejustknows commented on GitHub (Dec 19, 2024): OMG, running Ollama is so easy, but connect to it is so hard and require super deep advanced network/server/html knowledge. There are tons of posts all asking the same thing. I consider myself a pretty good old-school server manager. I spent like 2 hours tuning the env OLLAMA_ORIGINS and the caddy + HTML on a windows server, still getting the CORS. Now trying to setup a local proxy to forward the stupid thing. If running a non-standard service (simple handmade etc.) trying to connect to Ollama, it is a nightmare! Could Ollama just remove all the CORS restrict things, just run as a plaint service, let users handle their network port security etc please?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug good first issue
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/ollama#124
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?