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 #5041] Easy troubleshooting for Windows internal networks - known as "Connection refused" issue #3186

New Issue
Open
opened 2026-04-12 13:40:53 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 13:40:53 -05:00
Owner
Copy Link

Originally created by @HyperUpscale on GitHub (Jun 14, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5041

There is a very general issue with the sub networks that comes from the Automatically created networks in Windows:

if you have installed docker installed - you need to try to use as host address: host.docker.internal
if you have WSL installed and ollama on the Windows host - we need to use the IP that windows assigned IP for vEthernet(WSL) so WSL can find it - 172.X.X.X
if we use ollama on the WSL we need to use 127.0.0.1 to access it from the Windows host.

In any case we need to find Where ollama is "announced" by 0.0.0.0

Is there a way from the ollama Windows app - lets say as it is to indicate how ollama can be accessed so it will enable fast troubleshooting.

What I mean is, would it be possible to include indication in the taskbar icon to have that information easily?

For example something like this:
image

I believe that would be really useful

Originally created by @HyperUpscale on GitHub (Jun 14, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5041 There is a very general issue with the sub networks that comes from the Automatically created networks in Windows: if you have installed docker installed - you need to try to use as host address: **host.docker.internal** if you have WSL installed and ollama on the Windows host - we need to use the IP that windows assigned IP for vEthernet(WSL) so WSL can find it - **172.X.X.X** if we use ollama on the WSL we need to use **127.0.0.1** to access it from the Windows host. In any case we need to find Where ollama is "announced" by 0.0.0.0 Is there a way from the ollama Windows app - lets say as it is to indicate how ollama can be accessed so it will enable fast troubleshooting. What I mean is, would it be possible to include indication in the taskbar icon to have that information easily? For example something like this: ![image](https://github.com/ollama/ollama/assets/126105457/f45f1f14-1890-4aff-8dc3-d8f8a5584779) I believe that would be really useful
GiteaMirror added the feature request label 2026-04-12 13:40:53 -05:00
GiteaMirror commented 2026-04-12 13:40:54 -05:00
Author
Owner
Copy Link

@luojiyin1987 commented on GitHub (Jun 17, 2024):

you can use vscode attach WSL , config port forward.
image

<!-- gh-comment-id:2173655778 --> @luojiyin1987 commented on GitHub (Jun 17, 2024): you can use vscode attach WSL , config port forward. ![image](https://github.com/ollama/ollama/assets/6524977/2283ffe3-18ee-4445-9b4b-f139a4ffb9b0)
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#3186
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?