You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The settings page checks if the response to https://example.com is "Ollama is running". i have a setup where example.com is hosting an ollama web frontend and the reverseproxy proxypasses example.com/api to the ollama service. the result is, that the ollama app refuses the host, but it could use it
The text was updated successfully, but these errors were encountered:
But it seems like https://{openweb-ui-instance}/ollama/ always responds with {"status":true} no matter if Ollama integration is active or not, or if the users authorization headers are valid.
It would be great to be able to use this app even with Ollama API published behind a proxy application like OpenWeb UI
I hacked this together for myself. If you temporarily reverse proxy both the root path / and the ollama path /ollama/ to your Ollama instance you can convince the app to accept the settings. Then restore the reverse proxying to openwebui and it will continue working.
The settings page checks if the response to https://example.com is "Ollama is running". i have a setup where example.com is hosting an ollama web frontend and the reverseproxy proxypasses example.com/api to the ollama service. the result is, that the ollama app refuses the host, but it could use it
The text was updated successfully, but these errors were encountered: