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

Ollama error 404 #1819

Open
AlessioGesuelliUnicam opened this issue May 2, 2024 Discussed in #1710 · 1 comment
Open

Ollama error 404 #1819

AlessioGesuelliUnicam opened this issue May 2, 2024 Discussed in #1710 · 1 comment
Labels
bug Something isn't working

Comments

@AlessioGesuelliUnicam
Copy link

Discussed in #1710

Originally posted by AlessioGesuelliUnicam April 16, 2024
I don't know how resolve this problem
Ollama is running but langflow return Error 404

ValueError: Error: Ollama call
failed with status code 404. Maybe
your model is not found and you
should pull the model with ollama pull llama2:latest.

  • ERROR - chat - chat.py:57
    Error in chat websocket: control frame
    too long

Acquisizione schermata 16 04 2024 alle 16 32 37  1
Acquisizione schermata 16 04 2024 alle 16 32 37  2
Acquisizione schermata 16 04 2024 alle 16 32 57  1

Copy link

dosubot bot commented May 2, 2024

To resolve the Error 404 with Ollama in Langflow, ensure the base_url for the Ollama API in Langflow's configuration matches the actual endpoint where your Ollama API is hosted. If your Ollama API is not at the default "http://localhost:11434", update the base_url in the ChatOllamaComponent configuration to the correct URL. This step is crucial for Langflow to communicate with Ollama.

For the "control frame too long" error in your websocket connection, this issue arises when the websocket frame size exceeds the protocol or server's limit. To fix this, adjust the max_size parameter in your websocket server or client configuration to accommodate larger frames. Here’s an example using the websockets library in Python:

import websockets

# For a websocket server
start_server = websockets.serve(your_handler, "localhost", 6789, max_size=YourDesiredMaxSize)

# For a websocket client
async with websockets.connect('ws://yourserver:port', max_size=YourDesiredMaxSize) as websocket:
    # Your client code here

Replace YourDesiredMaxSize with a value that suits your application's needs, keeping in mind the balance between frame size and memory usage.

Details

Sources


About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

@dosubot dosubot bot added the bug Something isn't working label May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant