Llama3.2 Bug?

[ria]

Hi @Asadrz11014

I would try a few things here,

• update n8n and Ollama and make sure to use the latest Llama 3.2 model
• restart the services
• perhaps try running ollama separately and connect it via https://host.docker.internal:11434

You may also check out this similar community post:

Issue with Configuring Ollama in n8n Self-hosted AI Starter Kit

Thanks @ihortom ! Hi everyone, I managed to solve this issue and wanted to share the solution for others who might encounter the same problem. The root cause was that the starter kit requires explicitly specifying a profile (CPU or GPU) when starting the containers, but I was initially running it without any profile specified. Here’s how to fix it: First, stop and remove all existing containers: docker-compose down docker rm $(docker ps -a -q) 2. Then, launch the starter kit with the CPU…