Assistant Talk Bot 3.0.2 installed and enabled, but not active in conversation settings

[vawaver]

Hi,
I have installed and enabled the Assistant Talk Bot app version 3.0.2 on my Nextcloud AIO (version 30.0.8, Hub 9 / AIO v10.9.0) instance running on Ubuntu Server 24.04.

Active AI -> OpenAI

Unfortunately, in the conversation settings, the bot does not appear as active or running, even though the app itself is installed and started correctly.

Let me know if you need any logs or system information – happy to provide them.

[edward-ly]

Let me know if you need any logs or system information – happy to provide them.

Please do (system report, Nextcloud log, and Docker container log). I can't see any reason why the bot wouldn't be registered without them.

[vawaver]

System

Operating System: Linux 6.8.0-56-generic x86_64
CPU: Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz (12 threads)
Memory: 8.84 GB
Server time: Sat Mar 29 23:06:00 CET 2025
Uptime: 1 days, 2 hours, 45 minutes, 45 seconds
Version: 8.3.19
Memory limit: 512 MB
Max execution time: 3600
Upload max size: 16 GB
OPcache Revalidate Frequency: 60
Extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, ctype, curl, dom, fileinfo, filter, hash, iconv, json, mbstring, SPL, session, PDO, pdo_sqlite, bz2, posix, random, readline, Reflection, standard, SimpleXML, tokenizer, xml, xmlreader, xmlwriter, mysqlnd, cgi-fcgi, apcu, bcmath, Phar, exif, ftp, gd, gmp, igbinary, imagick, imap, intl, ldap, memcached, pcntl, pdo_pgsql, pgsql, redis, smbclient, sodium, sysvsem, zip, libsmbclient, Zend OPcache

---

Database
Type: pgsql
Version: PostgreSQL 16.8 on x86_64-pc-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
Size: 949,5 MB

Is it enough?

Nextcloud logs - nextcloud_2025_03_29.zip

nextcloud-aio-nextcloud docker logs - nextcloud-aio-nextcloud_logs.txt

Let me know whether it is what you have requested.

[vawaver]

Another screenshot from Administration settings -> Talk -> Bots.

[edward-ly]

NOTICE: PHP message: Client error: `POST http://nextcloud-aio-docker-socket-proxy:2375/v1.41/containers/nc_app_talk_bot_ai/start` resulted in a `404 Not Found` response:
No such container: nc_app_talk_bot_ai

This looks like an issue with either Nextcloud AIO or Docker Socket Proxy (or both) rather than the app itself. Pinging @szaimen @oleksandr-nc for clarification.

Also, it looks like the app container failed to start despite the app being registered on the NC side.

{
  "reqId": "3D9N3lAeGemBHy43JSpY",
  "level": 3,
  "time": "2025-03-28T19:12:01+00:00",
  "remoteAddr": "127.0.0.1",
  "user": "vawaver",
  "app": "PHP",
  "method": "POST",
  "url": "/apps/app_api/apps/enable/talk_bot_ai",
  "message": "Undefined array key \"State\" at /var/www/html/apps/app_api/lib/DeployActions/DockerActions.php#576",
  "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36",
  "version": "30.0.8.1",
  "data": {
    "app": "PHP"
  }
}
{
  "reqId": "3D9N3lAeGemBHy43JSpY",
  "level": 3,
  "time": "2025-03-28T19:12:01+00:00",
  "remoteAddr": "127.0.0.1",
  "user": "vawaver",
  "app": "PHP",
  "method": "POST",
  "url": "/apps/app_api/apps/enable/talk_bot_ai",
  "message": "Trying to access array offset on null at /var/www/html/apps/app_api/lib/DeployActions/DockerActions.php#576",
  "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36",
  "version": "30.0.8.1",
  "data": {
    "app": "PHP"
  }
}
{
  "reqId": "3D9N3lAeGemBHy43JSpY",
  "level": 3,
  "time": "2025-03-28T19:12:02+00:00",
  "remoteAddr": "127.0.0.1",
  "user": "vawaver",
  "app": "app_api",
  "method": "POST",
  "url": "/apps/app_api/apps/enable/talk_bot_ai",
  "message": "ExApp talk_bot_ai container startup failed.",
  "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36",
  "version": "30.0.8.1",
  "data": {
    "app": "app_api"
  }
}

[vawaver]

Ok. I hope that the guys will find a solution for that.

[oleksandr-nc]

Ok. I hope that the guys will find a solution for that.

Can you post the contents of the oc_ex_apps_daemons table. Feel free to replace haproxy_password content(it should contain encrypted password, but we interested in other fields)

[vawaver]

Ok. I hope that the guys will find a solution for that.

Can you post the contents of the oc_ex_apps_daemons table. Feel free to replace haproxy_password content(it should contain encrypted password, but we interested in other fields)

I like to do it but I am not an IT pro or even a programmer.
If you gave me the clear instructions step by step I will be glad to send you what you have requested.

[oleksandr-nc]

Maybe there was some bug in migration, and current deploy daemon has one expected value missing(judging from logs you provided).

One option will be be to recreate the Deploy Daemon, remember parameters you have for current one in AIO, delete it and create a new one(probably there is template for AIO deploy daemon)

[vawaver]

Update / follow-up

I revisited this after some time, but the bot still does not work.
As I already mentioned above, the Assistant Talk Bot does not appear at all in the list of bots / in conversation settings.

Environment:

• Nextcloud AIO: 11.9.0
• Nextcloud: 31.0.9
• Assistant Talk Bot: 3.1.2

Would it make sense to also involve @szaimen here for support?

[dcmumby]

i have seen this same problem , its crazy that such a touted feature simply doesn't work. I can chat with ai , generate text everything using the assistant app but nothing in talk !

[edward-ly]

Revisiting this now, but I'm unable to reproduce this with the latest versions of:

• Nextcloud AIO: 12.6.1 (latest channel)
• Nextcloud: 32.0.5
• Assistant Talk Bot: 3.1.3

I've also tried both the OpenAI app (3.10.0) and the llm2 app (2.6.0) for the AI backend, and I'm using the default settings for the Docker Socket Proxy AIO AppAPI daemon.

@vawaver I would suggest you try upgrading your AIO instance and see if that fixes your issue. If not, I would try asking for additional help in the forums or in the AIO repository, as I believe the issue is not related to the Talk Bot app (and more likely some misconfiguration in AIO). For that reason, I'll be closing this issue within the next week or two, but feel free to let me know if you disagree. Apologies for the delay in getting back to this.