github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-11 11:07:38 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #11920] Ollama 0.11.5-RC2 when launched from Start menu or auto-start is not listening on configuration #33672

New Issue
Closed
opened 2026-04-22 16:35:00 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-22 16:35:00 -05:00
Owner
Copy Link

Originally created by @MarkWard0110 on GitHub (Aug 15, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11920

Originally assigned to: @BruceMacD on GitHub.

What is the issue?

Windows 11
I have the System Environment variable OLLAMA_HOST=0.0.0.0 set and has been working for many of the previous versions. However, it seems 0.11.5-RC2 does not setup the host correctly when launched from the start menu or auto-start on boot.

previous logs

time=2025-08-15T06:00:54.474-05:00 level=INFO source=routes.go:1357 msg="Listening on [::]:11434 (version 0.11.4)"

When starting 0.11.5-RC2 from Start Menu or auto-start

time=2025-08-15T08:55:45.987-05:00 level=INFO source=routes.go:1358 msg="Listening on 127.0.0.1:11434 (version 0.11.5-rc2)"

If I open a new PowerShell terminal and start ollama serve it appears to use the environment variable

time=2025-08-15T08:59:49.791-05:00 level=INFO source=routes.go:1358 msg="Listening on [::]:11434 (version 0.11.5-rc2)"

Relevant log output

OS

Windows 11

GPU

RTX 3090

CPU

Intel Ultra 9 285K

Ollama version

0.11.5-RC2

Originally created by @MarkWard0110 on GitHub (Aug 15, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11920 Originally assigned to: @BruceMacD on GitHub. ### What is the issue? Windows 11 I have the System Environment variable `OLLAMA_HOST=0.0.0.0` set and has been working for many of the previous versions. However, it seems 0.11.5-RC2 does not setup the host correctly when launched from the start menu or auto-start on boot. previous logs ``` time=2025-08-15T06:00:54.474-05:00 level=INFO source=routes.go:1357 msg="Listening on [::]:11434 (version 0.11.4)" ``` When starting 0.11.5-RC2 from Start Menu or auto-start ``` time=2025-08-15T08:55:45.987-05:00 level=INFO source=routes.go:1358 msg="Listening on 127.0.0.1:11434 (version 0.11.5-rc2)" ``` If I open a new PowerShell terminal and start `ollama serve` it appears to use the environment variable ``` time=2025-08-15T08:59:49.791-05:00 level=INFO source=routes.go:1358 msg="Listening on [::]:11434 (version 0.11.5-rc2)" ``` ### Relevant log output ```shell ``` ### OS Windows 11 ### GPU RTX 3090 ### CPU Intel Ultra 9 285K ### Ollama version 0.11.5-RC2
GiteaMirror added the bug label 2026-04-22 16:35:00 -05:00
GiteaMirror commented 2026-04-22 16:35:03 -05:00
Author
Owner
Copy Link

@MarkWard0110 commented on GitHub (Aug 15, 2025):

Running from the terminal using ollama serve works

Running Ollama from Start Menu or Auto-Start. The ollama.exe and GUI connect to the server. Clients using something else in the server address does not work.

<!-- gh-comment-id:3191588696 --> @MarkWard0110 commented on GitHub (Aug 15, 2025): Running from the terminal using `ollama serve` works Running Ollama from Start Menu or Auto-Start. The ollama.exe and GUI connect to the server. Clients using something else in the server address does not work.
GiteaMirror commented 2026-04-22 16:35:03 -05:00
Author
Owner
Copy Link

@MarkWard0110 commented on GitHub (Aug 15, 2025):

To verify nothing is odd with my system, I reinstalled 0.11.4 and it works as expected.

time=2025-08-15T09:14:08.293-05:00 level=INFO source=routes.go:1357 msg="Listening on [::]:11434 (version 0.11.4)"
<!-- gh-comment-id:3191608686 --> @MarkWard0110 commented on GitHub (Aug 15, 2025): To verify nothing is odd with my system, I reinstalled 0.11.4 and it works as expected. ``` time=2025-08-15T09:14:08.293-05:00 level=INFO source=routes.go:1357 msg="Listening on [::]:11434 (version 0.11.4)" ```
GiteaMirror commented 2026-04-22 16:35:04 -05:00
Author
Owner
Copy Link

@MarkWard0110 commented on GitHub (Aug 15, 2025):

I think it is the ollama app.exe is what might be at play here.

If I use a terminal and launch the ollama app.exe

C:\Users\wardm\AppData\Local\Programs\Ollama> & '.\ollama app.exe'

time=2025-08-15T10:27:54.170-05:00 level=INFO source=routes.go:1358 msg="Listening on 127.0.0.1:11434 (version 0.11.5-rc2)"

In the same terminal if I run ollama serve

 >ollama serve
...
time=2025-08-15T10:28:27.772-05:00 level=INFO source=routes.go:1358 msg="Listening on [::]:11434 (version 0.11.5-rc2)"

I'm still trying to find a difference in the code diffs to see what might be the reason for this behavior

<!-- gh-comment-id:3191840251 --> @MarkWard0110 commented on GitHub (Aug 15, 2025): I think it is the `ollama app.exe` is what might be at play here. If I use a terminal and launch the `ollama app.exe` ``` C:\Users\wardm\AppData\Local\Programs\Ollama> & '.\ollama app.exe' ``` ``` time=2025-08-15T10:27:54.170-05:00 level=INFO source=routes.go:1358 msg="Listening on 127.0.0.1:11434 (version 0.11.5-rc2)" ``` In the same terminal if I run `ollama serve` ``` >ollama serve ... time=2025-08-15T10:28:27.772-05:00 level=INFO source=routes.go:1358 msg="Listening on [::]:11434 (version 0.11.5-rc2)" ``` I'm still trying to find a difference in the code diffs to see what might be the reason for this behavior
GiteaMirror commented 2026-04-22 16:35:05 -05:00
Author
Owner
Copy Link

@MarkWard0110 commented on GitHub (Aug 15, 2025):

My system environment variables

Image
<!-- gh-comment-id:3191848142 --> @MarkWard0110 commented on GitHub (Aug 15, 2025): My system environment variables <img width="459" height="262" alt="Image" src="https://github.com/user-attachments/assets/cb1f0c8d-044f-44dd-98ac-adbee673f19f" />
GiteaMirror commented 2026-04-22 16:35:05 -05:00
Author
Owner
Copy Link

@Justinius commented on GitHub (Aug 15, 2025):

I've seen something similar with the OLLAMA_MODELS env variable, on my setup. The Ollama app.exe seems to be loading the config from somewhere else (probably the SQL files they have now) whereas "ollama serve" works as before.

<!-- gh-comment-id:3192003644 --> @Justinius commented on GitHub (Aug 15, 2025): I've seen something similar with the OLLAMA_MODELS env variable, on my setup. The Ollama app.exe seems to be loading the config from somewhere else (probably the SQL files they have now) whereas "ollama serve" works as before.
GiteaMirror commented 2026-04-22 16:35:06 -05:00
Author
Owner
Copy Link

@BruceMacD commented on GitHub (Aug 15, 2025):

Thanks for the report. We've had some reports of the app not working with their remote ollama host, so I thought that moving where this environment variable was used would be a good fix. Turns out it was just confusing, so I've removed this change and let the OLLAMA_HOST pass through as normal. This will be fixed in the next and RC and upcoming release.

<!-- gh-comment-id:3192869500 --> @BruceMacD commented on GitHub (Aug 15, 2025): Thanks for the report. We've had some reports of the app not working with their remote ollama host, so I thought that moving where this environment variable was used would be a good fix. Turns out it was just confusing, so I've removed this change and let the OLLAMA_HOST pass through as normal. This will be fixed in the next and RC and upcoming release.
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#33672
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?