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

[GH-ISSUE #11468] Add Basic Auth (Username & Password) Support to Secure Remote Access #69629

New Issue
Open
opened 2026-05-04 18:43:09 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-04 18:43:09 -05:00
Owner
Copy Link

Originally created by @ravivarmanr-quantrail on GitHub (Jul 18, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11468

Originally assigned to: @pdevine on GitHub.

Issue Description

Problem
The Ollama CLI doesn't support HTTP Basic Authentication for remote connections.
This makes it difficult to securely share GPU resources with remote users or teammates over the internet.

Current Situation:

This works (proves auth works)

curl -u user:pass https://my-server.com/api/tags
Returns the list of models available on the server.

But this fails when trying to use ollama CLI:

export OLLAMA_HOST= https://my-server.com
ollama list
Error Output :
Error: something went wrong, please see the ollama server logs for details
11:33:43.291 IST HEAD / 401 Unauthorized

This shows that the server is correctly asking for authentication, but the Ollama CLI does not send credentials.

Originally created by @ravivarmanr-quantrail on GitHub (Jul 18, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11468 Originally assigned to: @pdevine on GitHub. ### **Issue Description** **Problem** The Ollama CLI doesn't support HTTP Basic Authentication for remote connections. This makes it difficult to securely share GPU resources with remote users or teammates over the internet. **Current Situation:** #### This works (proves auth works) `curl -u user:pass https://my-server.com/api/tags` Returns the list of models available on the server. #### But this fails when trying to use ollama CLI: `export OLLAMA_HOST= https://my-server.com` `ollama list` Error Output : `Error: something went wrong, please see the ollama server logs for details ` `11:33:43.291 IST HEAD / 401 Unauthorized` This shows that the server is correctly asking for authentication, but the Ollama CLI does not send credentials.
GiteaMirror added the feature request label 2026-05-04 18:43:09 -05:00
GiteaMirror commented 2026-05-04 18:43:11 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jul 18, 2025):

Ollama doesn't do authentication, that's normally handled by a proxy or other auth service. If you want a client that does auth, then you need to roll your own. The ollama cli is just a wrapper for the API, so writing a client that does auth is straightforward.

<!-- gh-comment-id:3089188268 --> @rick-github commented on GitHub (Jul 18, 2025): Ollama doesn't do authentication, that's normally handled by a proxy or other auth service. If you want a client that does auth, then you need to roll your own. The ollama cli is just a wrapper for the API, so writing a client that does auth is straightforward.
GiteaMirror commented 2026-05-04 18:43:11 -05:00
Author
Owner
Copy Link

@ravivarmanr-quantrail commented on GitHub (Jul 19, 2025):

Thanks for the clarification. I've raised a PR that adds Basic Auth support to the Ollama CLI using OLLAMA_USERNAME and OLLAMA_PASSWORD environment variables. This should help in scenarios where setting up a proxy isn't ideal.

Ollama doesn't do authentication, that's normally handled by a proxy or other auth service. If you want a client that does auth, then you need to roll your own. The ollama cli is just a wrapper for the API, so writing a client that does auth is straightforward.

<!-- gh-comment-id:3091946194 --> @ravivarmanr-quantrail commented on GitHub (Jul 19, 2025): Thanks for the clarification. I've raised a PR that adds Basic Auth support to the Ollama CLI using OLLAMA_USERNAME and OLLAMA_PASSWORD environment variables. This should help in scenarios where setting up a proxy isn't ideal. > Ollama doesn't do authentication, that's normally handled by a proxy or other auth service. If you want a client that does auth, then you need to roll your own. The ollama cli is just a wrapper for the API, so writing a client that does auth is straightforward.
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#69629
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?