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

[GH-ISSUE #5354] ollama should detect native windows proxy configuration #3352

New Issue
Open
opened 2026-04-12 13:57:53 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 13:57:53 -05:00
Owner
Copy Link

Originally created by @smallg0at on GitHub (Jun 28, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5354

Originally assigned to: @dhiltgen on GitHub.

What is the issue?

Ollama seems to fail to update itself in recent versions and app logs are as follow:

time=2024-06-28T11:23:56.487+08:00 level=INFO source=logging.go:50 msg="ollama app started"
time=2024-06-28T11:23:56.540+08:00 level=INFO source=server.go:176 msg="unable to connect to server"
time=2024-06-28T11:23:56.540+08:00 level=INFO source=server.go:135 msg="starting server..."
time=2024-06-28T11:23:56.547+08:00 level=INFO source=server.go:121 msg="started ollama server with pid 31184"
time=2024-06-28T11:23:56.547+08:00 level=INFO source=server.go:123 msg="ollama server logs C:\\Users\\<username>\\AppData\\Local\\Ollama\\server.log"
time=2024-06-28T11:24:00.238+08:00 level=INFO source=updater.go:102 msg="New update available at https://github.com/ollama/ollama/releases/download/v0.1.47/OllamaSetup.exe"
time=2024-06-28T11:24:00.257+08:00 level=ERROR source=updater.go:212 msg="failed to download new release: error checking update: Head \"https://github.com/ollama/ollama/releases/download/v0.1.47/OllamaSetup.exe\": dial tcp 127.0.0.1:443: connectex: No connection could be made because the target machine actively refused it."

I'm behind a proxy and its obviously not on the 443 port, and ollama server is not listening on it. running nslookup also shows the correct IP rather than localhost. So I have a suspicion that something in proxy detection has gone wrong...

OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.1.46

Originally created by @smallg0at on GitHub (Jun 28, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5354 Originally assigned to: @dhiltgen on GitHub. ### What is the issue? Ollama seems to fail to update itself in recent versions and app logs are as follow: ``` time=2024-06-28T11:23:56.487+08:00 level=INFO source=logging.go:50 msg="ollama app started" time=2024-06-28T11:23:56.540+08:00 level=INFO source=server.go:176 msg="unable to connect to server" time=2024-06-28T11:23:56.540+08:00 level=INFO source=server.go:135 msg="starting server..." time=2024-06-28T11:23:56.547+08:00 level=INFO source=server.go:121 msg="started ollama server with pid 31184" time=2024-06-28T11:23:56.547+08:00 level=INFO source=server.go:123 msg="ollama server logs C:\\Users\\<username>\\AppData\\Local\\Ollama\\server.log" time=2024-06-28T11:24:00.238+08:00 level=INFO source=updater.go:102 msg="New update available at https://github.com/ollama/ollama/releases/download/v0.1.47/OllamaSetup.exe" time=2024-06-28T11:24:00.257+08:00 level=ERROR source=updater.go:212 msg="failed to download new release: error checking update: Head \"https://github.com/ollama/ollama/releases/download/v0.1.47/OllamaSetup.exe\": dial tcp 127.0.0.1:443: connectex: No connection could be made because the target machine actively refused it." ``` I'm behind a proxy and its obviously not on the 443 port, and ollama server is not listening on it. running `nslookup` also shows the correct IP rather than localhost. So I have a suspicion that something in proxy detection has gone wrong... ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.1.46
GiteaMirror added the networkingfeature requestwindows labels 2026-04-12 13:57:53 -05:00
GiteaMirror commented 2026-04-12 13:57:54 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Jul 2, 2024):

Can you confirm you've set the proxy settings as described here and it still doesn't work?

<!-- gh-comment-id:2204428604 --> @dhiltgen commented on GitHub (Jul 2, 2024): Can you confirm you've set the proxy settings as described [here](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-do-i-use-ollama-behind-a-proxy) and it still doesn't work?
GiteaMirror commented 2026-04-12 13:57:55 -05:00
Author
Owner
Copy Link

@smallg0at commented on GitHub (Jul 3, 2024):

Can you confirm you've set the proxy settings as described here and it still doesn't work?

works now. but:

  • That should not be the intended method of getting the proxy on windows
  • Still couldn't explain why ollama decide to go for 127.0.0.1:443
<!-- gh-comment-id:2204922393 --> @smallg0at commented on GitHub (Jul 3, 2024): > Can you confirm you've set the proxy settings as described [here](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-do-i-use-ollama-behind-a-proxy) and it still doesn't work? works now. but: - That should not be the intended method of getting the proxy on windows - Still couldn't explain why ollama decide to go for `127.0.0.1:443`
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 networking windows
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#3352
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?