Re-opening issue #5044: SearXNG can't connect to Valkey.

[Ian-Marcel]

Link to issue searxng/searxng#5044 .
Hi, before anything, yes I am trying to add Valkey to my public instance, I am having the same Error 111, officially is:

valkey.exceptions.ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused.

Also tried the host.containers.internal and it hadn't changed a thing.

I'm using docker compose and this is my .yaml config:

services:
  # -- SeaXNG -- 
  searxng:
    container_name: "search.myinstance.com-searxng"
    image: searxng/searxng:latest
    networks:
      - searxng
    ports:
      - 127.0.0.1:2001:8080
    volumes:
      - searxng_config:/etc/searxng
      - searxng_data:/var/cache/searxng
    environment:
      - BASE_URL=http://localhost
      - SEARXNG_PORT=2001
      - SEARXNG_PUBLIC_INSTANCE=true
      - SEARXNG_VALKEY_URL=valkeys://127.0.0.1:6379/0
    logging:
      driver: "json-file"
      options:
        max-size: "1m"
        max-file: "1"
    restart: unless-stopped

  valkey:
    container_name: "search.myinstance.com-valkeyDB"
    image: valkey/valkey:alpine
    command: valkey-server --save 30 1 --loglevel warning --maxmemory 128mb --protected-mode no
    networks:
      - searxng
    ports:
      - 127.0.0.1:6379:6379
    volumes:
      - valkeyDB_config:/etc/valkey/
    logging:
      driver: "json-file"
      options:
        max-size: "1m"
        max-file: "1"
    restart: unless-stopped
    # -- SeaXNG -- 

  # Other Services...

networks:
  searxng:
    name: "search.myinstance.com"

volumes:
# -- SeaXNG -- 
  searxng_data:
    name: "search.myinstance.com-searxng-data"
    external: true
  searxng_config:
    name: "search.myinstance.com-searxng-config"
    external: true
  valkeyDB_config:
    name: "search.myinstance.com-valkeyDB-config"
    external: true
# -- SeaXNG --
    # ...

[inetol]

As both containers are in the same network, you could use the Valkey container name as a hostname directly valkey://search.myinstance.com-valkeyDB:6379 in SEARXNG_VALKEY_URL ENV.

By the way, we didn't test if Valkey works properly under TLS, as it's running in an isolated network shouldn't be kind of an issue here, so using the unencrypted proto (default) should be fine in your case.

[Ian-Marcel]

By the way, we didn't test if Valkey works properly under TLS, ...

You're right, I put valkeys: instead of valkey: to!

Btw I reverse proxy my container through nginx which handles the SSL/TLS, so this way I can keep this container not meant to be exposed to internet local, as far as I understand.
Now at least searxng return another error:

valkey.exceptions.TimeoutError: Timeout connecting to server

Not gonna lie, I'm very new to valkey(and redis-like DB's)

[Ian-Marcel]

Using Valkey's container_name(search.myinstance.com-valkeyDB:6379) works. also I was using valkeys: instead of valkey: plus I mistyped some parts of the URL! Thanks!