[GH-ISSUE #740] Using ollama-ui from remote client #349

Closed
opened 2026-04-12 09:59:33 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @suoko on GitHub (Oct 9, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/740

I have a server with ollama which works ok.
If I install ollama-ui or use the chrome extension (https://github.com/ollama-ui/ollama-ui) I can't reach the server from a remote client.
Let's say I have the server on 192.168.0.1 and the client on 192.168.0.2, how should I run the server ?
I tried both the OLLAMA_ORIGINS and OLLAMA_HOST options with no luck

Originally created by @suoko on GitHub (Oct 9, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/740 I have a server with ollama which works ok. If I install ollama-ui or use the chrome extension (https://github.com/ollama-ui/ollama-ui) I can't reach the server from a remote client. Let's say I have the server on 192.168.0.1 and the client on 192.168.0.2, how should I run the server ? I tried both the OLLAMA_ORIGINS and OLLAMA_HOST options with no luck
Author
Owner

@mxyng commented on GitHub (Oct 9, 2023):

How are you running the ollama service? OLLAMA_HOST and OLLAMA_ORIGINS need to be set in the same context as the service. For example, Linux systemd can be configured with a drop-in file:

# /etc/systemd/system/ollama.service.d/environment.conf
[Service]
Environment=OLLAMA_HOST=0.0.0.0
Environment=OLLAMA_ORIGINS=http://1.2.3.4
<!-- gh-comment-id:1753473571 --> @mxyng commented on GitHub (Oct 9, 2023): How are you running the ollama service? `OLLAMA_HOST` and `OLLAMA_ORIGINS` need to be set in the same context as the service. For example, Linux systemd can be configured with a drop-in file: ``` # /etc/systemd/system/ollama.service.d/environment.conf [Service] Environment=OLLAMA_HOST=0.0.0.0 Environment=OLLAMA_ORIGINS=http://1.2.3.4 ```
Author
Owner

@suoko commented on GitHub (Oct 10, 2023):

How are you running the ollama service? OLLAMA_HOST and OLLAMA_ORIGINS need to be set in the same context as the service. For example, Linux systemd can be configured with a drop-in file:

# /etc/systemd/system/ollama.service.d/environment.conf
[Service]
Environment=OLLAMA_HOST=0.0.0.0
Environment=OLLAMA_ORIGINS=http://1.2.3.4

Thanks, I had a wrong port set up in the ollama_host ip, I removed it and it works now

<!-- gh-comment-id:1755514521 --> @suoko commented on GitHub (Oct 10, 2023): > How are you running the ollama service? `OLLAMA_HOST` and `OLLAMA_ORIGINS` need to be set in the same context as the service. For example, Linux systemd can be configured with a drop-in file: > > ``` > # /etc/systemd/system/ollama.service.d/environment.conf > [Service] > Environment=OLLAMA_HOST=0.0.0.0 > Environment=OLLAMA_ORIGINS=http://1.2.3.4 > ``` Thanks, I had a wrong port set up in the ollama_host ip, I removed it and it works now
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#349