Assistant Talk Bot visible and enabled, but not responding

[vawaver]

🧠 Issue: Assistant Talk Bot visible and enabled, but not responding

Hey,
just to update the situation — I now have the Assistant Talk Bot visible and active in the system.

It correctly appears under
Administration → Talk → Bots,
and I can enable it inside conversations (as shown in the screenshots below).

However, the bot still doesn’t respond to any messages.
Even when it’s enabled in the room and I mention it with @assistant, there’s no reply or reaction at all — and no error message either.

So the issue is no longer that the bot isn’t available — it’s installed and visible,
but completely silent in the chat.

---

🧩 Environment

• Nextcloud AIO version: 32.0.1
• Server distribution: Ubuntu Server 24.04 (latest updates)
• Nextcloud edition: Nextcloud 25 Autumn
• Talk Bot version: 3.1.2
• Installation type: AIO (official Docker image)

---

📸 Screenshots

1️⃣ Conversation settings
(Assistant Talk Bot visible and enabled)

2️⃣ Talk administration settings
(Bot listed under Administration → Talk → Bots)

---

💬 Request

If anyone has already managed to get the Assistant Talk Bot working in Nextcloud 32 (AIO),
I’d really appreciate a hint on what else might be missing or misconfigured.

[edward-ly]

Sounds like a duplicate of #21. Just to make sure, are you seeing the same errors as posted in this comment?

[vawaver]

I am attaching latest logs Nextcloud + nextcloud-aio-nextcloud docker.

nextcloud.zip
_nextcloud-aio-nextcloud_logs.txt

[edward-ly]

Hm, I don't see anything in the AIO logs related to the app. What does your AppAPI deploy daemon configuration look like? It should be based on either the "All-in-One" template or the "HaRP All-in-One" template. The NC logs claim that the app is reachable at http://talk_bot_ai:23000/talk_bot_ai, which I'm not sure if it is correct or not.

[vawaver]

I’m using the default AIO setup for the mastercontainer, without any manual modifications.
The AppAPI deploy daemon configuration is therefore based on the standard AIO template, not HaRP.

Here’s my current docker-compose.yml for reference:

# version: "3.4"

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer  # must be named exactly like this!
    external: true

networks:
  default:
    name: nextcloud-aio                   # official AIO network created by the mastercontainer

services:
  nextcloud:
    image: ghcr.io/nextcloud-releases/all-in-one:latest
    restart: unless-stopped
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /etc/cups/client.conf:/etc/cups/client.conf:ro
      - /mnt/media_large/nextcloud_borg2:/mnt/media_large/nextcloud_borg2
    ports:
      - "6789:8080"  # Web UI of the mastercontainer (port for AIO installer)
    environment:
      - APACHE_PORT=11000
      - NEXTCLOUD_MEMORY_LIMIT=4096M
      - BORG_RETENTION_POLICY=--keep-daily=5

So the daemon should be using the default All-in-One AppAPI setup that AIO provides out of the box.