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 #5811] Ollama behind reverse proxy returns 404 #3622

New Issue
Closed
opened 2026-04-12 14:23:21 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-12 14:23:21 -05:00
Owner
Copy Link

Originally created by @rwjack on GitHub (Jul 20, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5811

What is the issue?

I have a complex proxy setup, but I can't seem to get Ollama set up.

user -> proxy -> ingress-proxy -> docker

services:
  ollama:
    image: ollama/ollama:latest
    ...
    ports:
      - "127.0.0.1:15007:11434"

When I curl 127.0.0.1:15007 from the docker host, I get the proper response Ollama is running#.

When I curl https://docker-host-fqdn:15443 -H "Host: ollama.hq.arpa" from the docker host (the ingress is on the docker host as well), I get a 404.

This leads me to believe that Ollama isn't accepting the request for some reason. I have 20+ other services which just work and all the proxy/ingress configuration is unified, so I'm unsure what else it can be other than some setting related to Ollama. I tried multiple different values in the OLLAMA_ORIGINS variable, including "*", but no joy.

OS

Linux

GPU

No response

CPU

No response

Ollama version

0.2.7

Originally created by @rwjack on GitHub (Jul 20, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5811 ### What is the issue? I have a complex proxy setup, but I can't seem to get Ollama set up. user -> proxy -> ingress-proxy -> docker ``` services: ollama: image: ollama/ollama:latest ... ports: - "127.0.0.1:15007:11434" ``` When I `curl 127.0.0.1:15007` from the docker host, I get the proper response `Ollama is running#`. When I `curl https://docker-host-fqdn:15443 -H "Host: ollama.hq.arpa"` from the docker host (the ingress is on the docker host as well), I get a 404. This leads me to believe that Ollama isn't accepting the request for some reason. I have 20+ other services which just work and all the proxy/ingress configuration is unified, so I'm unsure what else it can be other than some setting related to Ollama. I tried multiple different values in the OLLAMA_ORIGINS variable, including "*", but no joy. ### OS Linux ### GPU _No response_ ### CPU _No response_ ### Ollama version 0.2.7
GiteaMirror added the bug label 2026-04-12 14:23:21 -05:00
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#3622
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?