github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-09 01:59:50 -05:00
Code Issues 14.6k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #15077] Ollama 0.18.3 don't consider ollama.env, and so no longer reachable from distant host - FIXED not an ollama issue #35431

New Issue
Closed
opened 2026-04-22 19:55:55 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-22 19:55:55 -05:00
Owner
Copy Link

Originally created by @viba1 on GitHub (Mar 26, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15077

What is the issue?

After upgrading to Ollama 0.18.3, the server is no longer reachable from other machines on the local network (e.g. Open‑WebUI, n8n), even though the environment variable OLLAMA_HOST=0.0.0.0:11434 is correctly set.
With the previous version, the same configuration allowed access to the API from other LAN IPs without any issues.

Ollama version

0.18.3

Originally created by @viba1 on GitHub (Mar 26, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15077 ### What is the issue? After upgrading to Ollama 0.18.3, the server is no longer reachable from other machines on the local network (e.g. Open‑WebUI, n8n), even though the environment variable OLLAMA_HOST=0.0.0.0:11434 is correctly set. With the previous version, the same configuration allowed access to the API from other LAN IPs without any issues. ### Ollama version 0.18.3
GiteaMirror added the bug label 2026-04-22 19:55:55 -05:00
GiteaMirror commented 2026-04-22 19:55:56 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 26, 2026):

Works here.

time=2026-03-26T21:31:07.126+01:00 level=INFO source=routes.go:1798 msg="Listening on [::]:11435 (version 0.18.3)"
[GIN] 2026/03/26 - 21:31:27 | 200 |      97.728µs |    10.10.22.186 | GET      "/"

Server logs will aid in debugging.

<!-- gh-comment-id:4138025240 --> @rick-github commented on GitHub (Mar 26, 2026): Works here. ``` time=2026-03-26T21:31:07.126+01:00 level=INFO source=routes.go:1798 msg="Listening on [::]:11435 (version 0.18.3)" [GIN] 2026/03/26 - 21:31:27 | 200 | 97.728µs | 10.10.22.186 | GET "/" ``` [Server logs](https://docs.ollama.com/troubleshooting) will aid in debugging.
GiteaMirror commented 2026-04-22 19:55:57 -05:00
Author
Owner
Copy Link

@viba1 commented on GitHub (Mar 26, 2026):

my problem is the following: after update to 0.18.3, ollama no longer considers ollama.env.

<!-- gh-comment-id:4138184708 --> @viba1 commented on GitHub (Mar 26, 2026): my problem is the following: after update to 0.18.3, ollama no longer considers ollama.env.
GiteaMirror commented 2026-04-22 19:55:57 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 26, 2026):

What is ollama.env?

<!-- gh-comment-id:4138204087 --> @rick-github commented on GitHub (Mar 26, 2026): What is ollama.env?
GiteaMirror commented 2026-04-22 19:55:58 -05:00
Author
Owner
Copy Link

@viba1 commented on GitHub (Mar 26, 2026):

See here for exemple: https://github.com/peterjohannmedina/IntelArc_NoRebar

<!-- gh-comment-id:4138221061 --> @viba1 commented on GitHub (Mar 26, 2026): See here for exemple: https://github.com/peterjohannmedina/IntelArc_NoRebar
GiteaMirror commented 2026-04-22 19:55:58 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 26, 2026):

Standard ollama doesn't use .env files.

<!-- gh-comment-id:4138238821 --> @rick-github commented on GitHub (Mar 26, 2026): Standard ollama doesn't use .env files.
GiteaMirror commented 2026-04-22 19:55:58 -05:00
Author
Owner
Copy Link

@viba1 commented on GitHub (Mar 26, 2026):

Lot of project are using environment files
Other exemple : https://github.com/bhza/ollama-deep-researcher
It seems to be broken

<!-- gh-comment-id:4138245146 --> @viba1 commented on GitHub (Mar 26, 2026): Lot of project are using environment files Other exemple : https://github.com/bhza/ollama-deep-researcher It seems to be broken
GiteaMirror commented 2026-04-22 19:55:59 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 26, 2026):

Lot of project are using environment files

Maybe so, ollama doesn't, that's done by the service framework. IntelArc_NoRebar includes a line in the service to use the the env file:

EnvironmentFile=/etc/ollama/ollama.env

I suspect that you had this configured in the main service file and it was overwritten when you upgraded to 0.18.3. If you want to continue to use this method, it needs to be added to the override file for the service. Run sudo systemctl edit ollama and add the EnvironmentFile line to a section titled [Service].

<!-- gh-comment-id:4138278389 --> @rick-github commented on GitHub (Mar 26, 2026): > Lot of project are using environment files Maybe so, ollama doesn't, that's done by the service framework. IntelArc_NoRebar includes a line in the service to use the the env file: ``` EnvironmentFile=/etc/ollama/ollama.env ``` I suspect that you had this configured in the main service file and it was overwritten when you upgraded to 0.18.3. If you want to continue to use this method, it needs to be added to the override file for the service. Run `sudo systemctl edit ollama` and add the `EnvironmentFile` line to a section titled `[Service]`.
GiteaMirror commented 2026-04-22 19:55:59 -05:00
Author
Owner
Copy Link

@viba1 commented on GitHub (Mar 26, 2026):

I've already tried it: it no longer works. It still worked before this migration to 0.18.3
I've also tried to add to the PATH with the same result

<!-- gh-comment-id:4138294881 --> @viba1 commented on GitHub (Mar 26, 2026): I've already tried it: it no longer works. It still worked before this migration to 0.18.3 I've also tried to add to the PATH with the same result
GiteaMirror commented 2026-04-22 19:56:00 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 26, 2026):

What's the output of systemctl --no-pager cat ollama.

<!-- gh-comment-id:4138305635 --> @rick-github commented on GitHub (Mar 26, 2026): What's the output of `systemctl --no-pager cat ollama`.
GiteaMirror commented 2026-04-22 19:56:00 -05:00
Author
Owner
Copy Link

@viba1 commented on GitHub (Mar 26, 2026):

Ok. I think i've fix my issue.
Problem was link to access rights on .ollama directory after upgrading.
I don't think it an ollama issue.
Could be closed. Sorry.
Thanks for your help.

<!-- gh-comment-id:4138376169 --> @viba1 commented on GitHub (Mar 26, 2026): Ok. I think i've fix my issue. Problem was link to access rights on .ollama directory after upgrading. I don't think it an ollama issue. Could be closed. Sorry. Thanks for your help.
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#35431
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?