github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #14367] Environment (OLLAMA_HOST) not working on Debian 13 #35096

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

Originally created by @Jchimbo on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14367

What is the issue?

Description

I have set up an Ollama instance locally on my Debian 13 server within my network. The setup involves the following environment variables:

  • OLLAMA_HOST=0.0.0.0:11434
  • OLLAMA_ORIGINS=*

The application runs successfully when accessed from a Windows machine (dual-booted with Debian 13), but fails to run through ollama cli (The browser can access Ollama Server) on the Debian 13 boot of that machine, where the environment variables are set up identically( OLLAMA_HOST=192.168.1.33). Specifically, it gives this error message:
Ollama.service:

● ollama.service - Ollama Service Loaded: loaded (/etc/systemd/system/ollama.service; enabled; preset: enabled) Drop-In: /etc/systemd/system/ollama.service.d └─override.conf Active: activating (auto-restart) (Result: exit-code) since Sun 2026-02-22 19:15:48 EST; 624ms ago Invocation: 780fb3bfed87442392f2feda01bd1631 Process: 12491 ExecStart=/usr/local/bin/ollama serve (code=exited, status=1/FAILURE) Main PID: 12491 (code=exited, status=1/FAILURE) Mem peak: 10.5M CPU: 37ms

Journalctl:
Feb 22 17:12:20 user1-WS ollama[178780]: Error: listen tcp 192.168.1.33:11434: bind: cannot assign requested address Feb 22 17:12:20 user1-WS systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE Feb 22 17:12:20 user1-WS systemd[1]: ollama.service: Failed with result 'exit-code'. Feb 22 17:12:22 user1-WS systemd[1]: Stopped ollama.service - Ollama Service.

Steps to Reproduce

  1. Set up a Debian 13 server via 'curl -fsSL https://ollama.com/install.sh | sh''.
  2. Install Ollama and configure it with environment variables:
    • OLLAMA_HOST=0.0.0.0:11434
    • OLLAMA_ORIGINS=*
  3. Set up Ollama client on Debian 13 via ''curl -fsSL https://ollama.com/install.sh | sh''
  4. Set Environment variable via Sudo systemctl edit ollama.service:

[Service]
Environment="OLLAMA_HOST=http://192.168.1.33:11434"
4.Attempt to run the application on the same Debian 13 machine where the setup is configured identically to windows.

Expected vs Actual Behavior

Expected: The Ollama instance should run and be accessible via OLLAMA_HOST=0.0.0.0:11434 from both machines.
Actual: The application fails to run on the Debian 13 machine, showing an error related to binding of requested address via OLLAMA_HOST.

Environment Details

Operating System: Debian 13
Ollama Version: 0.16.3
Network Configuration: Local network setup

Relevant log output

Feb 22 17:12:20 user1-WS ollama[178780]: Error: listen tcp 192.168.1.33:11434: bind: cannot assign requested address
Feb 22 17:12:20 user1-WS systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE
Feb 22 17:12:20 user1-WS systemd[1]: ollama.service: Failed with result 'exit-code'.
Feb 22 17:12:22 user1-WS systemd[1]: Stopped ollama.service - Ollama Service.

OS

Linux

GPU

Nvidia

CPU

Intel

Ollama version

0.16.3

Originally created by @Jchimbo on GitHub (Feb 23, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14367 ### What is the issue? ### Description I have set up an Ollama instance locally on my Debian 13 server within my network. The setup involves the following environment variables: - OLLAMA_HOST=0.0.0.0:11434 - OLLAMA_ORIGINS=* The application runs successfully when accessed from a Windows machine (dual-booted with Debian 13), but fails to run through ollama cli (The browser can access Ollama Server) on the Debian 13 boot of that machine, where the environment variables are set up identically( OLLAMA_HOST=192.168.1.33). Specifically, it gives this error message: Ollama.service: ``● ollama.service - Ollama Service Loaded: loaded (/etc/systemd/system/ollama.service; enabled; preset: enabled) Drop-In: /etc/systemd/system/ollama.service.d └─override.conf Active: activating (auto-restart) (Result: exit-code) since Sun 2026-02-22 19:15:48 EST; 624ms ago Invocation: 780fb3bfed87442392f2feda01bd1631 Process: 12491 ExecStart=/usr/local/bin/ollama serve (code=exited, status=1/FAILURE) Main PID: 12491 (code=exited, status=1/FAILURE) Mem peak: 10.5M CPU: 37ms `` Journalctl: ``Feb 22 17:12:20 user1-WS ollama[178780]: Error: listen tcp 192.168.1.33:11434: bind: cannot assign requested address Feb 22 17:12:20 user1-WS systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE Feb 22 17:12:20 user1-WS systemd[1]: ollama.service: Failed with result 'exit-code'. Feb 22 17:12:22 user1-WS systemd[1]: Stopped ollama.service - Ollama Service. `` ### Steps to Reproduce 1. Set up a Debian 13 server via 'curl -fsSL https://ollama.com/install.sh | sh''. 2. Install Ollama and configure it with environment variables: - OLLAMA_HOST=0.0.0.0:11434 - OLLAMA_ORIGINS=* 3. Set up Ollama client on Debian 13 via ''curl -fsSL https://ollama.com/install.sh | sh'' 4. Set Environment variable via Sudo systemctl edit ollama.service: `[Service]` `Environment="OLLAMA_HOST=http://192.168.1.33:11434" ` 4.Attempt to run the application on the same Debian 13 machine where the setup is configured identically to windows. ### Expected vs Actual Behavior Expected: The Ollama instance should run and be accessible via OLLAMA_HOST=0.0.0.0:11434 from both machines. Actual: The application fails to run on the Debian 13 machine, showing an error related to binding of requested address via OLLAMA_HOST. ### Environment Details Operating System: Debian 13 Ollama Version: 0.16.3 Network Configuration: Local network setup ### Relevant log output ```shell Feb 22 17:12:20 user1-WS ollama[178780]: Error: listen tcp 192.168.1.33:11434: bind: cannot assign requested address Feb 22 17:12:20 user1-WS systemd[1]: ollama.service: Main process exited, code=exited, status=1/FAILURE Feb 22 17:12:20 user1-WS systemd[1]: ollama.service: Failed with result 'exit-code'. Feb 22 17:12:22 user1-WS systemd[1]: Stopped ollama.service - Ollama Service. ``` ### OS Linux ### GPU Nvidia ### CPU Intel ### Ollama version 0.16.3
GiteaMirror added the bug label 2026-04-22 19:18:38 -05:00
GiteaMirror commented 2026-04-22 19:18:41 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Feb 23, 2026):

On the client, don't set OLLAMA_HOST=http://192.168.1.33:11434 in the server config. If you want only outbound ollama connections from the client, remove OLLAMA_HOST from the config file and add it to the client environment, eg in your .bashrc (or whatever startup file your shell uses if not bash).

<!-- gh-comment-id:3942035448 --> @rick-github commented on GitHub (Feb 23, 2026): On the client, don't set `OLLAMA_HOST=http://192.168.1.33:11434` in the server config. If you want only outbound ollama connections from the client, remove `OLLAMA_HOST` from the config file and add it to the client environment, eg in your .bashrc (or whatever startup file your shell uses if not bash).
GiteaMirror commented 2026-04-22 19:18:43 -05:00
Author
Owner
Copy Link

@Jchimbo commented on GitHub (Feb 23, 2026):

That fixed the issue. Thank you so much.

<!-- gh-comment-id:3942058519 --> @Jchimbo commented on GitHub (Feb 23, 2026): That fixed the issue. Thank you so much.
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#35096
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?