[GH-ISSUE #9056] setting OLLAMA_HOST to 0.0.0.0 could make the API to listen on the port using IPv6 only #83580

Closed
opened 2026-05-09 18:36:46 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @MDBrothers on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/9056

What is the issue?

https://github.com/ollama/ollama/issues/3961#issue-2266535771

This issue still persists as of the 0.3.13 version distributed via Ubuntu snaps

The issue I am referencing had been closed without comment, yet I am several users have encountered this problem after it had been deemed closed.

Relevant log output


OS

Linux

GPU

Nvidia

CPU

AMD

Ollama version

0.3.13

Originally created by @MDBrothers on GitHub (Feb 12, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/9056 ### What is the issue? https://github.com/ollama/ollama/issues/3961#issue-2266535771 This issue still persists as of the 0.3.13 version distributed via Ubuntu snaps The issue I am referencing had been closed without comment, yet I am several users have encountered this problem after it had been deemed closed. ### Relevant log output ```shell ``` ### OS Linux ### GPU Nvidia ### CPU AMD ### Ollama version 0.3.13
GiteaMirror added the bug label 2026-05-09 18:36:46 -05:00
Author
Owner

@rick-github commented on GitHub (Feb 12, 2025):

If setting OLLAMA_HOST=0.0.0.0 binds to ipv6 only that would appear to be a network configuration problem for the OS. Linux usually has a dual-stack system and listens on both ip4 and ip6 interfaces for the wildcard address unless configured otherwise.

$ list=(0.0.0.0 [::] 127.0.0.1 [::1] 10.10.109.113 [fda8:ce99:1519::700]) ; for i in ${list[*]} ; do OLLAMA_HOST="$i" ollama serve >&- 2>&- & pid=$! ; sleep 2 ; for j in ${list[*]:2:5} ; do printf "%-21s %-21s %s\n" "$i" "$j" "$(curl -s "$j:11434")" ; done ; kill $pid ; sleep 1 ; done
server                client
0.0.0.0               127.0.0.1             Ollama is running
0.0.0.0               [::1]                 Ollama is running
0.0.0.0               10.10.109.113         Ollama is running
0.0.0.0               [fda8:ce99:1519::700] Ollama is running

[::]                  127.0.0.1             Ollama is running
[::]                  [::1]                 Ollama is running
[::]                  10.10.109.113         Ollama is running
[::]                  [fda8:ce99:1519::700] Ollama is running

127.0.0.1             127.0.0.1             Ollama is running
127.0.0.1             [::1]                 
127.0.0.1             10.10.109.113         
127.0.0.1             [fda8:ce99:1519::700] 

[::1]                 127.0.0.1             
[::1]                 [::1]                 Ollama is running
[::1]                 10.10.109.113         
[::1]                 [fda8:ce99:1519::700] 

10.10.109.113         127.0.0.1             
10.10.109.113         [::1]                 
10.10.109.113         10.10.109.113         Ollama is running
10.10.109.113         [fda8:ce99:1519::700] 

[fda8:ce99:1519::700] 127.0.0.1             
[fda8:ce99:1519::700] [::1]                 
[fda8:ce99:1519::700] 10.10.109.113         
[fda8:ce99:1519::700] [fda8:ce99:1519::700] Ollama is running

<!-- gh-comment-id:2654998815 --> @rick-github commented on GitHub (Feb 12, 2025): If setting OLLAMA_HOST=0.0.0.0 binds to ipv6 only that would appear to be a network configuration problem for the OS. Linux usually has a dual-stack system and listens on both ip4 and ip6 interfaces for the wildcard address unless configured otherwise. ```console $ list=(0.0.0.0 [::] 127.0.0.1 [::1] 10.10.109.113 [fda8:ce99:1519::700]) ; for i in ${list[*]} ; do OLLAMA_HOST="$i" ollama serve >&- 2>&- & pid=$! ; sleep 2 ; for j in ${list[*]:2:5} ; do printf "%-21s %-21s %s\n" "$i" "$j" "$(curl -s "$j:11434")" ; done ; kill $pid ; sleep 1 ; done server client 0.0.0.0 127.0.0.1 Ollama is running 0.0.0.0 [::1] Ollama is running 0.0.0.0 10.10.109.113 Ollama is running 0.0.0.0 [fda8:ce99:1519::700] Ollama is running [::] 127.0.0.1 Ollama is running [::] [::1] Ollama is running [::] 10.10.109.113 Ollama is running [::] [fda8:ce99:1519::700] Ollama is running 127.0.0.1 127.0.0.1 Ollama is running 127.0.0.1 [::1] 127.0.0.1 10.10.109.113 127.0.0.1 [fda8:ce99:1519::700] [::1] 127.0.0.1 [::1] [::1] Ollama is running [::1] 10.10.109.113 [::1] [fda8:ce99:1519::700] 10.10.109.113 127.0.0.1 10.10.109.113 [::1] 10.10.109.113 10.10.109.113 Ollama is running 10.10.109.113 [fda8:ce99:1519::700] [fda8:ce99:1519::700] 127.0.0.1 [fda8:ce99:1519::700] [::1] [fda8:ce99:1519::700] 10.10.109.113 [fda8:ce99:1519::700] [fda8:ce99:1519::700] Ollama is running ```
Author
Owner

@MDBrothers commented on GitHub (Feb 13, 2025):

Okay so for anyone else who was having difficulty the problems seemed to be this:

  • the ipv6 thing was irrelevant to the real issue
  • my router was blocking local ICMP traffic which was apparently interfering with things.
  • My security settings on my Mac for the Vscode app were not allowing it to communicate with devices on my network
<!-- gh-comment-id:2657860419 --> @MDBrothers commented on GitHub (Feb 13, 2025): Okay so for anyone else who was having difficulty the problems seemed to be this: - the ipv6 thing was irrelevant to the real issue - my router was blocking local ICMP traffic which was apparently interfering with things. - My security settings on my Mac for the Vscode app were not allowing it to communicate with devices on my network
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#83580