Timeout after 5 Minutes

[mohamed3nan]

Did you try this:

http://localhost:11434/v1

??

[Rex_Mundi]

@mohamed3nan

http://localhost:11434/v1

Ah like that. Now different error.

and also thanks for trying to fix it with me.

[mohamed3nan]

and u sure you tried the ollama here with and without v1?

Timeout after 5 Minutes

here: [image] Also, make sure the URL is actually working and reachable.

also look here if your setup the same:

Error with Ollama Chat model integrating with AI Agent Node

Hi there! Thank you for the response. I’ve tried to update the base URL with v1 and I get the following error: [image] However, when I remove the V1, it works [image] When I try typing the curl command, it looks like it works ➜ ~ curl http://ollama.coburgcrescent.lan:11434/v1/chat/completions \ -H "Content-Type: application/json" \ -H "Authorization: Bearer ollama" \ -d '{"model":"llama3.1:8b","messages":[{"role":"user","content":"Hello"}]}' {"id":"chatcmpl-300","object":"chat.comp…

Cannot fetch ollama3.2 model from docker

Describe the problem/error/question I have n8n running in a docker container and i have in docker 2 versions of llama llm. 1st llm model i have installed in this way: first i pull llama image by running command: docker pull ollama/ollama:latest then i run the docker container in cpu mode using command: docker run -d -v ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama then i run the model using this command: docker exec -it ollama ollama run llama3 this model runs well, in n8n…

[BrianM]

Just sharing that i have the same issue. I use a local LLM (LM Studio) on ubuntu at http://llm.lan:1234/v1/. Some of the queries can take a long time to process, if the ai agent doesn’t get a response back within 5 minutes it kills the connection and my LLM sees the client disconnecting. I’ve tried increasing all the timeouts, still has issues. Some of the adjustments help a little like increasing the 60000ms timeout. There are times when I’m going to throw so much data at it that it takes an hour to crunch it, but this really shouldn’t be an issue apart from having tools to mitigate runaway workflows when you need them. Currently I have workflows with chat model calls that are right at 5 minutes and I’m having to use other solutions when n8n should be the champ for what I’m doing. Even my Open WebUI will process all these same prompts/tools.

I’ve also observed that there seem to be behavior differences when using a chat trigger vs a schedule trigger (chat trigger seems to time out faster). I’m a new n8n user so I could well be missing the obvious.

I’m happy to try any solutions, but I would invite n8n to test a case where the chat model takes longer than 5 minutes to respond; see if you hit a hard ceiling of 5 minute timeout.

[Wouter_Nigrini]

Hi @Rex_Mundi

FYI, when trying to point to another container on Docker, localhost from n8n wont work as it will try and find that server on the n8n container (localhost). You need to use either a docker compose service name or find the docker internal host IP using the below:

http://host.docker.internal:11434