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

[GH-ISSUE #10376] Allow Ollama to use http:// instead of https:// to connect to the registry #6820

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

Originally created by @Daniel-Nashed on GitHub (Apr 22, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10376

The main reason for this feature request is to add a caching proxy before the Ollama registry without tricking around with certificates.

Proxies like Squid can cache http:// requests very well.

Even the registry is https:// an NGINX server could be used to cache the blobs.
The same works very well with Linux repositories hosted over http://.
In case of Ollama the blobs are protected with SHA256 checksums, so there would be no loss.

On the other side if the Ollama registry would also have an http:// endpoint this could greatly reduce CPU usage on both ends.

It looks like there is currently no parameter to change DefaultProtocolScheme.

I would wish both would be available

  • A way to specify http:// and maybe change the target address
  • Have an http:// endpoint for the registry

Thanks for considering this request. It would reduce energy consumption as well if the option would be available as well.

Originally created by @Daniel-Nashed on GitHub (Apr 22, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10376 The main reason for this feature request is to add a caching proxy before the Ollama registry without tricking around with certificates. Proxies like Squid can cache http:// requests very well. Even the registry is https:// an NGINX server could be used to cache the blobs. The same works very well with Linux repositories hosted over http://. In case of Ollama the blobs are protected with SHA256 checksums, so there would be no loss. On the other side if the Ollama registry would also have an http:// endpoint this could greatly reduce CPU usage on both ends. It looks like there is currently no parameter to change `DefaultProtocolScheme`. I would wish both would be available - A way to specify http:// and maybe change the target address - Have an http:// endpoint for the registry Thanks for considering this request. It would reduce energy consumption as well if the option would be available as well.
GiteaMirror added the feature request label 2026-04-12 18:37:09 -05:00
GiteaMirror commented 2026-04-12 18:37:12 -05:00
Author
Owner
Copy Link

@robo47 commented on GitHub (Mar 9, 2026):

Having multiple ollama servers in my network, i would really love a solution for this too, which does not require creating a CA and importing it on all systems.

<!-- gh-comment-id:4026927941 --> @robo47 commented on GitHub (Mar 9, 2026): Having multiple ollama servers in my network, i would really love a solution for this too, which does not require creating a CA and importing it on all systems.
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 feature request
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#6820
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?