Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to a host only providing /api #38

Open
lomenzel opened this issue Aug 2, 2024 · 3 comments
Open

Connecting to a host only providing /api #38

lomenzel opened this issue Aug 2, 2024 · 3 comments

Comments

@lomenzel
Copy link

lomenzel commented Aug 2, 2024

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

@Pietro395
Copy link

I have the same problem

@Manut38
Copy link

Manut38 commented Oct 18, 2024

I'm using OpenWeb UI and ran into the same issue.

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

@kudos
Copy link

kudos commented Dec 3, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants