github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-10 07:43:10 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

Ollama server inaccessible when requested from different network #25

New Issue
Closed
opened 2025-11-11 14:02:23 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-11 14:02:23 -06:00
Owner
Copy Link

Originally created by @Notarin on GitHub (Nov 6, 2023).

When hosting ollama on host1, and ollama-webui on host1, and attempting to access via host2 on a seperate network, the webui will refuse to connect to ollama, while working on host1.

To Reproduce

  • Install & Run Ollama
  • Install & Run Ollama WebUI
  • Port Forward
  • Attempt to access from any client other than the locally on server
    It would be expected to function appropriately, however it for whatever reason pretends as if it cannot connect to the Ollama server, despite working just fine locally. Even if you port forward Ollama and point it to the public Ollama endpoint (verified) it will still not work whatsoever.

image
image

Server:

  • OS: Arch Linux
  • Version: v1.0.0-alpha

Client:

  • OS: Windows 11
  • Browser: Chrome Developer Channel
Originally created by @Notarin on GitHub (Nov 6, 2023). When hosting ollama on host1, and ollama-webui on host1, and attempting to access via host2 on a seperate network, the webui will refuse to connect to ollama, while working on host1. **To Reproduce** - Install & Run Ollama - Install & Run Ollama WebUI - Port Forward - Attempt to access from any client other than the locally on server It would be expected to function appropriately, however it for whatever reason pretends as if it cannot connect to the Ollama server, despite working just fine locally. Even if you port forward Ollama and point it to the public Ollama endpoint (verified) it will *still* not work whatsoever. ![image](https://github.com/ollama-webui/ollama-webui/assets/25104390/22aa3a27-5694-485a-b95d-976b03bbafc9) ![image](https://github.com/ollama-webui/ollama-webui/assets/25104390/191057ad-3e39-40ef-96b2-c71b2b6dd9bd) **Server:** - OS: Arch Linux - Version: v1.0.0-alpha **Client:** - OS: Windows 11 - Browser: Chrome Developer Channel
GiteaMirror commented 2025-11-11 14:02:24 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Nov 6, 2023):

Hi, most likely a CORS problem. Were you able to check everything outlined in the troubleshooting section in readme.md? If you did and still experiencing the same issue, it would be helpful if you could provide a console log from your browser's developer tool. Thanks.

@tjbck commented on GitHub (Nov 6, 2023): Hi, most likely a CORS problem. Were you able to check everything outlined in the troubleshooting section in readme.md? If you did and still experiencing the same issue, it would be helpful if you could provide a console log from your browser's developer tool. Thanks.
GiteaMirror commented 2025-11-11 14:02:24 -06:00
Author
Owner
Copy Link

@Notarin commented on GitHub (Nov 6, 2023):

image
strange, it appears to be not obeying the provided parameter

@Notarin commented on GitHub (Nov 6, 2023): ![image](https://github.com/ollama-webui/ollama-webui/assets/25104390/dcdccb7c-f1d2-4aea-8e84-163e78d25455) strange, it appears to be not obeying the provided parameter
GiteaMirror commented 2025-11-11 14:02:24 -06:00
Author
Owner
Copy Link

@Notarin commented on GitHub (Nov 6, 2023):

changing the default in the env file appears to have the expected effect.
I was under the false assumption that the requests were run server side, and was testing the public url via the settings menu.

@Notarin commented on GitHub (Nov 6, 2023): changing the default in the env file appears to have the expected effect. I was under the false assumption that the requests were run server side, and was testing the public url via the settings menu.
GiteaMirror commented 2025-11-11 14:02:24 -06:00
Author
Owner
Copy Link

@Notarin commented on GitHub (Nov 6, 2023):

the only issue now is that setting the url via the settings menu is not working, should i rename this issue or make a new one?

@Notarin commented on GitHub (Nov 6, 2023): the only issue now is that setting the url via the settings menu is not working, should i rename this issue or make a new one?
GiteaMirror commented 2025-11-11 14:02:25 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Nov 6, 2023):

#70 should fix the issue. Please try again by building from the latest commit and let me know how it goes, Thanks!

@tjbck commented on GitHub (Nov 6, 2023): #70 should fix the issue. Please try again by building from the latest commit and let me know how it goes, Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
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/open-webui#25
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?