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

[GH-ISSUE #11503] Ollama IPv4 Binding Issue on Ubuntu #7599

New Issue
Closed
opened 2026-04-12 19:41:08 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 19:41:08 -05:00
Owner
Copy Link

Originally created by @panairi on GitHub (Jul 23, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11503

What is the issue?

An Ollama instance running as a systemd service on an Ubuntu computer was inaccessible from other machines on a Tailscale network. The initial investigation revealed that the Ollama service was only listening on IPv6 (tcp6 :::11434) and not on any IPv4 addresses, which was the root cause of the connection failure.

Troubleshooting Summary
A series of extensive troubleshooting steps were taken to configure the service to listen on IPv4 (0.0.0.0).

Systemd Configuration: Standard and advanced systemd override methods were employed to set the OLLAMA_HOST="0.0.0.0" environment variable. This included both setting the Environment variable and directly modifying the ExecStart command.

Error Resolution: The configuration changes led to a series of secondary errors that were successfully resolved:

Address In Use: A crash loop caused by a lingering "ghost" process was fixed by identifying and terminating the conflicting process.

Permission Denied: A "factory reset" of the application's settings (by moving its home directory) led to a startup failure due to file permissions. This was resolved by manually recreating the home directory and assigning correct ownership to the ollama user.

Final State: After resolving all intermediate configuration conflicts and application errors, the Ollama service starts cleanly and runs without crashing. However, it stubbornly reverts to its original behavior, listening only on IPv6 and completely ignoring the correctly configured OLLAMA_HOST environment variable designed to enable IPv4 listening.

Conclusion
The system's service configuration is now correct and clean according to best practices. The persistence of the issue strongly indicates an application-level bug within this specific version of Ollama, where the binary does not honor its own environment variables for network configuration on the host system. The recommended next step is to report the issue to the Ollama developers and attempt to update the application.

Relevant log output

OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @panairi on GitHub (Jul 23, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11503 ### What is the issue? An Ollama instance running as a systemd service on an Ubuntu computer was inaccessible from other machines on a Tailscale network. The initial investigation revealed that the Ollama service was only listening on IPv6 (tcp6 :::11434) and not on any IPv4 addresses, which was the root cause of the connection failure. Troubleshooting Summary A series of extensive troubleshooting steps were taken to configure the service to listen on IPv4 (0.0.0.0). Systemd Configuration: Standard and advanced systemd override methods were employed to set the OLLAMA_HOST="0.0.0.0" environment variable. This included both setting the Environment variable and directly modifying the ExecStart command. Error Resolution: The configuration changes led to a series of secondary errors that were successfully resolved: Address In Use: A crash loop caused by a lingering "ghost" process was fixed by identifying and terminating the conflicting process. Permission Denied: A "factory reset" of the application's settings (by moving its home directory) led to a startup failure due to file permissions. This was resolved by manually recreating the home directory and assigning correct ownership to the ollama user. Final State: After resolving all intermediate configuration conflicts and application errors, the Ollama service starts cleanly and runs without crashing. However, it stubbornly reverts to its original behavior, listening only on IPv6 and completely ignoring the correctly configured OLLAMA_HOST environment variable designed to enable IPv4 listening. Conclusion The system's service configuration is now correct and clean according to best practices. The persistence of the issue strongly indicates an application-level bug within this specific version of Ollama, where the binary does not honor its own environment variables for network configuration on the host system. The recommended next step is to report the issue to the Ollama developers and attempt to update the application. ### Relevant log output ```shell ``` ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bug label 2026-04-12 19:41:08 -05:00
GiteaMirror commented 2026-04-12 19:41:10 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jul 23, 2025):

#9056

<!-- gh-comment-id:3110466017 --> @rick-github commented on GitHub (Jul 23, 2025): #9056
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#7599
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?