github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-15 20:54:54 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #7000] Respect the Access-Control-Allow-Private-Network in Chrome #30194

New Issue
Open
opened 2026-04-22 09:43:04 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-22 09:43:04 -05:00
Owner
Copy Link

Originally created by @PaulKinlan on GitHub (Sep 27, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7000

What is the issue?

I'm testing ollama from an environment hosted on repl.it running in the browser. I have a local version of ollama running with the OLLAMA_HOST=*, https://48a38c67-3eda-41cf-804b-e04fba963d55-00-14tthqngapcgy.worf.replit.dev (other variations result in the same error).

It looks like the new Access-Control-Allow-Private-Network is starting to be enforced when accessing the ollama server from a non-localhost origin.

Chrome: 129.0.6668.58 - Works
Chrome: 131.0.6742.0 - Fails with the error Access to fetch at 'http://127.0.0.1:11434/api/generate' from origin 'https://48a38c67-3eda-41cf-804b-e04fba963d55-00-14tthqngapcgy.worf.replit.dev' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Private-Network' header was present in the preflight response for this private network request targeting the local address space.

It looks like somewhere between these two versions, we (Chrome) started to enforce requiring the response from locally hosted ollama servers to require Access-Control-Allow-Private-Network: true HTTP Header.

OS

Linux, macOS, Windows

GPU

Apple

CPU

Apple

Ollama version

0.3.12

Originally created by @PaulKinlan on GitHub (Sep 27, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7000 ### What is the issue? I'm testing ollama from an environment hosted on repl.it running in the browser. I have a local version of ollama running with the `OLLAMA_HOST=*, https://48a38c67-3eda-41cf-804b-e04fba963d55-00-14tthqngapcgy.worf.replit.dev` (other variations result in the same error). It looks like the new `Access-Control-Allow-Private-Network` is starting to be enforced when accessing the ollama server from a non-localhost origin. Chrome: 129.0.6668.58 - Works Chrome: 131.0.6742.0 - Fails with the error `Access to fetch at 'http://127.0.0.1:11434/api/generate' from origin 'https://48a38c67-3eda-41cf-804b-e04fba963d55-00-14tthqngapcgy.worf.replit.dev' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Private-Network' header was present in the preflight response for this private network request targeting the `local` address space.` It looks like somewhere between these two versions, we (Chrome) started to enforce requiring the response from locally hosted ollama servers to require `Access-Control-Allow-Private-Network: true` HTTP Header. ### OS Linux, macOS, Windows ### GPU Apple ### CPU Apple ### Ollama version 0.3.12
GiteaMirror added the bug label 2026-04-22 09:43:04 -05:00
GiteaMirror commented 2026-04-22 09:43:05 -05:00
Author
Owner
Copy Link

@G4Zz0L1 commented on GitHub (Mar 11, 2025):

Any news for this?
I'm on chrome 134.0.6998.35, this setting is preventing ollama to work with host http://localhost:11434, from other addresses.

<!-- gh-comment-id:2712259313 --> @G4Zz0L1 commented on GitHub (Mar 11, 2025): Any news for this? I'm on chrome 134.0.6998.35, this setting is preventing ollama to work with host http://localhost:11434, from other addresses.
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
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#30194
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?