Skip to content

Goose tries to connect to Ollama on the wrong port #2003

@sammcj

Description

@sammcj

Describe the bug

Goose seems to be incorrectly appending a port at the end of the Ollama host URL:

Pictured below you can see the URL to my Ollama server, except Goose has added ':11434' which is not a port I configured in the Ollama server URL (it's standard HTTPS, 443 in this case).

A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behaviour:

  1. Set your Ollama server URL to something valid such as https://ollama.my.network
  2. Try to use Goose
  3. Experience error
  4. Note that the URL in the error has had the default localhost Ollama port appended to it

Expected behaviour

Goose to respect Ollama server URLs

Screenshots

Image

Please provide following information:

  • OS & Arch: macOS (client), Fedora (server)
  • Interface: UI
  • Version: 1.0.16
  • Extensions enabled: N/A
  • Provider & Model: Ollama, Any

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions