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

[PR #13079] [MERGED] app/ui: fix to point ollama client to ui backend in dev mode #14066

New Issue
Closed
opened 2026-04-13 00:43:50 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 00:43:50 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/13079
Author: @hoyyeva
Created: 11/13/2025
Status: ✅ Merged
Merged: 11/17/2025
Merged by: @hoyyeva

Base: main ← Head: hoyyeva/fix-app-dev-mode

📝 Commits (3)

  • ff9741b fix api returns 404 due to calling wrong port in dev mode
  • 2e54b3b fix: point ollama client to ui backend in dev mode
  • bd0c676 address comment

📊 Changes

3 files changed (+13 additions, -3 deletions)

View changed files

📝 app/ui/app/src/api.ts (+1 -2)
➕ app/ui/app/src/lib/config.ts (+10 -0)
📝 app/ui/app/src/lib/ollama-client.ts (+2 -1)

📄 Description

In development mode, the Ollama client was using window.location.origin (http://localhost:5173 since frontend is running on 5173), causing it to call APIs on the Vite dev server instead of the UI backend proxy server. This resulted in 404 errors for some API calls (/tags, /show).

This PR fix to configure the Ollama client to use http://127.0.0.1:3001 in dev mode, which is where the UI backend server (started with -dev flag) listens and proxies requests to the Ollama server.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/13079 **Author:** [@hoyyeva](https://github.com/hoyyeva) **Created:** 11/13/2025 **Status:** ✅ Merged **Merged:** 11/17/2025 **Merged by:** [@hoyyeva](https://github.com/hoyyeva) **Base:** `main` ← **Head:** `hoyyeva/fix-app-dev-mode` --- ### 📝 Commits (3) - [`ff9741b`](https://github.com/ollama/ollama/commit/ff9741b2ede9ae2e61343151e7492e8bbb2c7c73) fix api returns 404 due to calling wrong port in dev mode - [`2e54b3b`](https://github.com/ollama/ollama/commit/2e54b3b625baa00beeed9c8b2f447acd7ad4c5b2) fix: point ollama client to ui backend in dev mode - [`bd0c676`](https://github.com/ollama/ollama/commit/bd0c6767bccd75c0ac21948bb0e6839cc9b0d647) address comment ### 📊 Changes **3 files changed** (+13 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `app/ui/app/src/api.ts` (+1 -2) ➕ `app/ui/app/src/lib/config.ts` (+10 -0) 📝 `app/ui/app/src/lib/ollama-client.ts` (+2 -1) </details> ### 📄 Description In development mode, the Ollama client was using window.location.origin (http://localhost:5173 since frontend is running on 5173), causing it to call APIs on the Vite dev server instead of the UI backend proxy server. This resulted in 404 errors for some API calls (/tags, /show). This PR fix to configure the Ollama client to use http://127.0.0.1:3001 in dev mode, which is where the UI backend server (started with -dev flag) listens and proxies requests to the Ollama server. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 00:43:50 -05:00
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 pull-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#14066
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?