ollama - 💡(How to fix) Fix Ollama 0.18.3 don't consider ollama.env, and so no longer reachable from distant host - FIXED not an ollama issue [10 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
ollama/ollama#15077Fetched 2026-04-08 01:36:30
View on GitHub
Comments
10
Participants
2
Timeline
15
Reactions
0
Author
Participants
Timeline (top)
commented ×10renamed ×3closed ×1labeled ×1
RAW_BUFFERClick to expand / collapse

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

extent analysis

Fix Plan

The fix involves updating the Ollama configuration to ensure it binds to the correct IP address and port.

  • Check the ollama.yml configuration file for the host setting and update it to 0.0.0.0:11434 if necessary.
  • Alternatively, you can use the --host command-line flag when starting Ollama, like this: ollama --host 0.0.0.0:11434.
  • If you are using a Docker container, update the docker run command to include the -p flag, mapping the container port to the host port: docker run -p 11434:11434 ollama.

Example ollama.yml configuration:

host: 0.0.0.0:11434

Example command-line flag:

ollama --host 0.0.0.0:11434

Example Docker run command:

docker run -p 11434:11434 ollama

Verification

To verify that the fix worked, try accessing the Ollama API from another machine on the local network using a tool like curl:

curl http://<ollama-server-ip>:11434

Replace <ollama-server-ip> with the IP address of the machine running Ollama.

Extra Tips

Make sure to check the Ollama documentation for any specific configuration requirements for your version. Additionally, ensure that any firewalls or network security groups are configured to allow incoming traffic on port 11434.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

ollama - 💡(How to fix) Fix Ollama 0.18.3 don't consider ollama.env, and so no longer reachable from distant host - FIXED not an ollama issue [10 comments, 2 participants]