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 #7280] When server is bound to 0.0.0.0, it should allow also communication redirected by netsh to localhost (issue specific to with WSL2) #4626

New Issue
Open
opened 2026-04-12 15:32:17 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-12 15:32:17 -05:00
Owner
Copy Link

Originally created by @mmb78 on GitHub (Oct 20, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7280

I have ollama server running within WSL2, on Win10. I want to access it from outside. The WSL2 needs to extra tricks to get the network traffic to reach it.

When I set a netsh rule that takes the outside traffic (allowed by Win firewall) and redirects to "WSL2-IP":11434
netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=64065 connectaddress=172.18.200.13 connectport=11434

it all works when ollama config has this:
Environment="OLLAMA_HOST=0.0.0.0"

I can connect to: http://"machine IP":64065
and get ollama to respond!

But the problem is that the WSL2 IP is dynamic and will change .. so ideally I would use this netsh rule:
netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=64065 connectaddress=localhost connectport=11434
and just keep ollama listening only on localhost

but this somehow does not work and the communication is lost.

Interestingly enough using localhost in netsh for open-webui sever works well!

Maybe I miss some issue but I could not find another solution to this.

Originally created by @mmb78 on GitHub (Oct 20, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7280 I have ollama server running within WSL2, on Win10. I want to access it from outside. The WSL2 needs to extra tricks to get the network traffic to reach it. When I set a netsh rule that takes the outside traffic (allowed by Win firewall) and redirects to "WSL2-IP":11434 netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=64065 connectaddress=172.18.200.13 connectport=11434 it all works when ollama config has this: Environment="OLLAMA_HOST=0.0.0.0" I can connect to: http://"machine IP":64065 and get ollama to respond! But the problem is that the WSL2 IP is dynamic and will change .. so ideally I would use this netsh rule: netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=64065 connectaddress=localhost connectport=11434 and just keep ollama listening only on localhost but this somehow does not work and the communication is lost. Interestingly enough using localhost in netsh for open-webui sever works well! Maybe I miss some issue but I could not find another solution to this.
GiteaMirror added the wslfeature requestwindows labels 2026-04-12 15:32:17 -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 feature request windows wsl
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#4626
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?