[BUG]

[Argentumkuh]

Describe the bug
I have a simple flow with conversational chain, ollama chat, running in the common docker compose stack with flowise (I'm using container alias in the Flowise configuration for ollama IP), ollama embeddings, in-memory vector store and plain text document nodes. As I can see in logs, flowise tries to call /api/embeddings ollama endpoint with GET request for any operation as Chat or Upsert with 404 error code in response, so operations are failing. I suggest - there is no such endpoint in current ollama build, so I think it is something wrong with Flowise ollama node.

To Reproduce
Steps to reproduce:

1. Create flow like in the example
2. Click on Upsert or Chat button
3. In case of Chat - write some message and send it
4. Wait some time
5. See error 404 not found
   Expected behavior
   Chat or Upsert operations are passing successfully

Screenshots
Screenshots with my flow configuration and containers logs are added.

Setup

• Installation: Docker Desktop v 4.34.0
• Flowise v 2.2.4 (latest in moment)
• OS: Windows
• Browser Mozilla, Chrome

Additional context
Docker Compose file is added.

`version: '3.1'

services:
flowise:
image: flowiseai/flowise
restart: always
environment:
- PORT=${PORT}
- CORS_ORIGINS=${CORS_ORIGINS}
- IFRAME_ORIGINS=${IFRAME_ORIGINS}
- FLOWISE_USERNAME=${FLOWISE_USERNAME}
- FLOWISE_PASSWORD=${FLOWISE_PASSWORD}
- FLOWISE_FILE_SIZE_LIMIT=${FLOWISE_FILE_SIZE_LIMIT}
- DEBUG=${DEBUG}
- DATABASE_PATH=${DATABASE_PATH}
- DATABASE_TYPE=${DATABASE_TYPE}
- DATABASE_PORT=${DATABASE_PORT}
- DATABASE_HOST=${DATABASE_HOST}
- DATABASE_NAME=${DATABASE_NAME}
- DATABASE_USER=${DATABASE_USER}
- DATABASE_PASSWORD=${DATABASE_PASSWORD}
- DATABASE_SSL=${DATABASE_SSL}
- DATABASE_SSL_KEY_BASE64=${DATABASE_SSL_KEY_BASE64}
- APIKEY_STORAGE_TYPE=${APIKEY_STORAGE_TYPE}
- APIKEY_PATH=${APIKEY_PATH}
- SECRETKEY_PATH=${SECRETKEY_PATH}
- FLOWISE_SECRETKEY_OVERWRITE=${FLOWISE_SECRETKEY_OVERWRITE}
- LOG_LEVEL=${LOG_LEVEL}
- LOG_PATH=${LOG_PATH}
- BLOB_STORAGE_PATH=${BLOB_STORAGE_PATH}
- DISABLE_FLOWISE_TELEMETRY=${DISABLE_FLOWISE_TELEMETRY}
- MODEL_LIST_CONFIG_JSON=${MODEL_LIST_CONFIG_JSON}
- GLOBAL_AGENT_HTTP_PROXY=${GLOBAL_AGENT_HTTP_PROXY}
- GLOBAL_AGENT_HTTPS_PROXY=${GLOBAL_AGENT_HTTPS_PROXY}
- GLOBAL_AGENT_NO_PROXY=${GLOBAL_AGENT_NO_PROXY}
- DISABLED_NODES=${DISABLED_NODES}
ports:
- '${PORT}:${PORT}'
volumes:
- ~/.flowise:/root/.flowise
entrypoint: /bin/sh -c "sleep 3; flowise start"
ollama:
container_name: ollama
image: ollama/ollama
ports:
- "11434:11434"
deploy:
resources:
reservations:
devices:
- driver: nvidia
capabilities: [ "gpu" ]
count: all`

[timothycarambat]

Use host.docker.internal not localhost. Localhost in docker will loopback into the container, not the host.
#3108 (comment)

[Argentumkuh]

Use host.docker.internal not localhost. Localhost in docker will loopback into the container, not the host. #3108 (comment)

I tried, and can say, that it doesn't matters, what IP to use. The difference, is that in case of host.docker.internal request is sending via docker gateway, and in case of alias using - to container directly. Also I didn't use localhost before. The problem still presents with the same error.

[Argentumkuh]

Possibly this /api/ps API endpoint must be used instead of /api/embeddings. According to ollama documentation: https://github.com/ollama/ollama/blob/main/docs/api.md#generate-embeddings