8000 How to access remote Ollama server domain · Issue #1668 · block/goose · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

How to access remote Ollama server domain #1668

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.

Sign up for GitHub

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

Jump to bottom
Open
clickbrain opened this issue Mar 13, 2025 · 3 comments
Open

How to access remote Ollama server domain #1668

clickbrain opened this issue Mar 13, 2025 · 3 comments
Labels
core Pertains to core goose functionality enhancement New feature or request

Comments

@clickbrain
Copy link
clickbrain commented Mar 13, 2025 •
edited
Loading

I have ollama hosted on a Mac Studio and have a domain mapped to the Ollama URL on that server:
https://ollama.mydomain.com. Unfortunately, it looks like Goose adds :11434/v1/chat/completions to the end of whatever host a user puts into the Ollama setup field. Is there anyway to make sure it doesn't do that and just maps to the endpoint of the URL I provided?

I am assuming that is why I am getting the "Ran into this error: Execution error: error sending request for url" message, because I have Qwen 2.5 in Ollama on the remote server.
@wendytang
Copy link
Collaborator

Would it be possible to set up a reverse proxy? Like

server {
    listen 443 ssl;
    server_name ollama.mydomain.com;

    location / {
        proxy_pass http://127.0.0.1:11434;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}

@wendytang wendytang added the core Pertains to core goose functionality label Mar 14, 2025
@cbruyndoncx
Copy link

maybe adding the :80 port is enough for goose to not do that ?

@meenalc meenalc added the enhancement New feature or request label Mar 20, 2025
@Richie765
Copy link

I'm running into the same problem.

I have Ollama running on https://ollama.mydomain.com.

When I entered this URL in Goose (Desktop), it would try to access it on port 11434 instead of 443. After some effort, I added the url with the :443 port and now I get this error:

Ran into this error: Execution error: error sending request for url (https://ollama.mydomain.com/v1/chat/completions).

When I click on this link, it goes to the browser and this URL does not exist.

I looked into the Ollama API documentation at https://github.com/ollama/ollama/blob/main/docs/api.md and there all URL's begin with /api/ and there is nothing that ends with /chat/completions or /completions

Also I noticed that if I change the URL within Goose, I always have to Quit and Restart Goose before it takes effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
core Pertains to core goose functionality enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@clickbrain @cbruyndoncx @Richie765 @meenalc @wendytang
0