github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-15 12:48:05 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #12878] APP OLLAMA: Add support for specifying IP:port of a remote Ollama server #8532

New Issue
Open
opened 2026-04-12 21:14:08 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-12 21:14:08 -05:00
Owner
Copy Link

Originally created by @sanio11 on GitHub (Oct 31, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12878

Currently, the Ollama app only connects to a local instance (localhost). There is no option to define a remote host, for example when running an Ollama server on another machine in the same network or in the cloud.

Current Behavior

The app assumes http://127.0.0.1:11434 as the default endpoint.

There is no configuration option to change this address.

Desired Behavior

Allow users to set a custom server address and port, such as:

http://192.168.1.10:11434

The app should send API requests to this remote endpoint instead of the local one.

This could be exposed either through a configuration field (e.g. OLLAMA_HOST environment variable) or an in-app setting.

Motivation

Many users run Ollama on dedicated servers or more powerful machines. Enabling remote connectivity would make it possible to use those instances from other devices on the same network or via VPN, improving flexibility and performance.

Originally created by @sanio11 on GitHub (Oct 31, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12878 Currently, the Ollama app only connects to a local instance (localhost). There is no option to define a remote host, for example when running an Ollama server on another machine in the same network or in the cloud. Current Behavior The app assumes http://127.0.0.1:11434 as the default endpoint. There is no configuration option to change this address. Desired Behavior Allow users to set a custom server address and port, such as: http://192.168.1.10:11434 The app should send API requests to this remote endpoint instead of the local one. This could be exposed either through a configuration field (e.g. OLLAMA_HOST environment variable) or an in-app setting. Motivation Many users run Ollama on dedicated servers or more powerful machines. Enabling remote connectivity would make it possible to use those instances from other devices on the same network or via VPN, improving flexibility and performance.
GiteaMirror added the feature request label 2026-04-12 21:14:08 -05:00
GiteaMirror commented 2026-04-12 21:14:10 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Oct 31, 2025):

Set OLLAMA_HOST and restart the app.

<!-- gh-comment-id:3471991453 --> @rick-github commented on GitHub (Oct 31, 2025): Set `OLLAMA_HOST` and restart the app.
GiteaMirror commented 2026-04-12 21:14:11 -05:00
Author
Owner
Copy Link

@sanio11 commented on GitHub (Nov 3, 2025):

Set OLLAMA_HOST and restart the app.

I have setted OLLAMA_HOST in env variabiles windows, but the app ollama not connect to remote llm

<!-- gh-comment-id:3479184139 --> @sanio11 commented on GitHub (Nov 3, 2025): > Set `OLLAMA_HOST` and restart the app. I have setted OLLAMA_HOST in env variabiles windows, but the app ollama not connect to remote llm
GiteaMirror commented 2026-04-12 21:14:11 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Nov 3, 2025):

Open a CMD window, run the following and post the output to this issue:

set | findstr OLLAMA
<!-- gh-comment-id:3482181566 --> @rick-github commented on GitHub (Nov 3, 2025): Open a CMD window, run the following and post the output to this issue: ```text set | findstr OLLAMA ```
GiteaMirror commented 2026-04-12 21:14:12 -05:00
Author
Owner
Copy Link

@sanio11 commented on GitHub (Nov 14, 2025):

Open a CMD window, run the following and post the output to this issue:

set | findstr OLLAMA

set | findstr OLLAMA
OLLAMA_HOST=192.168.188.50:11434

internal port opened, ping ok, telnet to verify port ok!

<!-- gh-comment-id:3531308050 --> @sanio11 commented on GitHub (Nov 14, 2025): > Open a CMD window, run the following and post the output to this issue: > > ``` > set | findstr OLLAMA > ``` set | findstr OLLAMA OLLAMA_HOST=192.168.188.50:11434 internal port opened, ping ok, telnet to verify port ok!
GiteaMirror commented 2026-04-12 21:14:12 -05:00
Author
Owner
Copy Link

@sonofagl1tch commented on GitHub (Nov 19, 2025):

pr for the UI app https://github.com/ollama/ollama/pull/13147

<!-- gh-comment-id:3553445670 --> @sonofagl1tch commented on GitHub (Nov 19, 2025): pr for the UI app https://github.com/ollama/ollama/pull/13147
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 feature request
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#8532
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?