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.
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).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/67
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.
**Server:**
- OS: Arch Linux
- Version: v1.0.0-alpha
**Client:**
- OS: Windows 11
- Browser: Chrome Developer Channel
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.
<!-- gh-comment-id:1794285342 -->
@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.
strange, it appears to be not obeying the provided parameter
<!-- gh-comment-id:1794336505 -->
@Notarin commented on GitHub (Nov 6, 2023):
strange, it appears to be not obeying the provided parameter
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.
<!-- gh-comment-id:1794340279 -->
@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.
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?
<!-- gh-comment-id:1794349073 -->
@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?
#70 should fix the issue. Please try again by building from the latest commit and let me know how it goes, Thanks!
<!-- gh-comment-id:1794381332 -->
@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!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Notarin on GitHub (Nov 6, 2023).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/67
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
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.
Server:
Client:
@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.
@Notarin commented on GitHub (Nov 6, 2023):
strange, it appears to be not obeying the provided parameter
@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):
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?
@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!