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 #2560] Error: Head "http://127.0.0.1:11434/": EOF (Windows 10) #1501

New Issue
Closed
opened 2026-04-12 11:24:52 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-12 11:24:52 -05:00
Owner
Copy Link

Originally created by @EdwHA on GitHub (Feb 17, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2560

Thank you for the OLLAMA.
So far, I've been using ollama in WSL2, and when the windows version came out, I experienced it right away. But..

Microsoft Windows [Version 10.0.19045.4046]
C:\Users\Name>ollama pull nous-hermes:13b-llama2-q6_K
Error: Head "http://127.0.0.1:11434/": EOF

C:\Users\Name>ollama list
Error: Head "http://127.0.0.1:11434/": EOF

ollama help provides a normal help

from app.log:
...
time=2024-02-17T13:20:54.375+03:00 level=WARN source=server.go:109 msg="server crash 16 - exit code 1 - respawning"
time=2024-02-17T13:20:54.875+03:00 level=ERROR source=server.go:112 msg="failed to restart server exec: already started"
time=2024-02-17T13:21:10.884+03:00 level=WARN source=server.go:109 msg="server crash 17 - exit code 1 - respawning"
time=2024-02-17T13:21:11.385+03:00 level=ERROR source=server.go:112 msg="failed to restart server exec: already started"

from server.log:
...
Error: listen tcp 127.0.0.1:11434: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
Error: listen tcp 127.0.0.1:11434: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
Error: listen tcp 127.0.0.1:11434: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

Originally created by @EdwHA on GitHub (Feb 17, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2560 Thank you for the OLLAMA. So far, I've been using ollama in WSL2, and when the windows version came out, I experienced it right away. But.. Microsoft Windows [Version 10.0.19045.4046] C:\Users\Name>ollama pull nous-hermes:13b-llama2-q6_K Error: Head "http://127.0.0.1:11434/": EOF C:\Users\Name>ollama list Error: Head "http://127.0.0.1:11434/": EOF ollama help provides a normal help from app.log: ... time=2024-02-17T13:20:54.375+03:00 level=WARN source=server.go:109 msg="server crash 16 - exit code 1 - respawning" time=2024-02-17T13:20:54.875+03:00 level=ERROR source=server.go:112 msg="failed to restart server exec: already started" time=2024-02-17T13:21:10.884+03:00 level=WARN source=server.go:109 msg="server crash 17 - exit code 1 - respawning" time=2024-02-17T13:21:11.385+03:00 level=ERROR source=server.go:112 msg="failed to restart server exec: already started" from server.log: ... Error: listen tcp 127.0.0.1:11434: bind: An attempt was made to access a socket in a way forbidden by its access permissions. Error: listen tcp 127.0.0.1:11434: bind: An attempt was made to access a socket in a way forbidden by its access permissions. Error: listen tcp 127.0.0.1:11434: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
GiteaMirror commented 2026-04-12 11:24:53 -05:00
Author
Owner
Copy Link

@thdevai commented on GitHub (Feb 18, 2024):

I had this problem and I discovered that it was because I had added a portproxy to be able to access the ollama API from Windows that was running on WSL2.

To see if this is it, run this command in cmd:

netsh interface portproxy show all

If so, you need to remove it with this command:

netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=127.0.0.1

or

netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=0.0.0.0

<!-- gh-comment-id:1950690705 --> @thdevai commented on GitHub (Feb 18, 2024): I had this problem and I discovered that it was because I had added a portproxy to be able to access the ollama API from Windows that was running on WSL2. To see if this is it, run this command in cmd: netsh interface portproxy show all If so, you need to remove it with this command: netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=127.0.0.1 or netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=0.0.0.0
GiteaMirror commented 2026-04-12 11:24:53 -05:00
Author
Owner
Copy Link

@EdwHA commented on GitHub (Feb 18, 2024):

I had this problem and I discovered that it was because I had added a portproxy to be able to access the ollama API from Windows that was running on WSL2.

To see if this is it, run this command in cmd:

netsh interface portproxy show all

If so, you need to remove it with this command:

netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=127.0.0.1

or

netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=0.0.0.0

Thanks, it solved my problem.

<!-- gh-comment-id:1951188139 --> @EdwHA commented on GitHub (Feb 18, 2024): > I had this problem and I discovered that it was because I had added a portproxy to be able to access the ollama API from Windows that was running on WSL2. > > To see if this is it, run this command in cmd: > > netsh interface portproxy show all > > If so, you need to remove it with this command: > > netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=127.0.0.1 > > or > > netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=0.0.0.0 Thanks, it solved my problem.
GiteaMirror commented 2026-04-12 11:24:54 -05:00
Author
Owner
Copy Link

@szymonk92 commented on GitHub (Feb 21, 2024):

Same error, no proxy

<!-- gh-comment-id:1956202439 --> @szymonk92 commented on GitHub (Feb 21, 2024): Same error, no proxy
GiteaMirror commented 2026-04-12 11:24:54 -05:00
Author
Owner
Copy Link

@tzzed commented on GitHub (Sep 2, 2024):

Hello I solved the same issue see here

<!-- gh-comment-id:2325221472 --> @tzzed commented on GitHub (Sep 2, 2024): Hello I solved the same issue see [here](https://github.com/ollama/ollama/issues/2627#issuecomment-2325218799)
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
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#1501
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?