Continuation of investigation – Context Chat Backend behaviour in Nextcloud AIO

ℹ️ Support
,
1

Continuation of investigation – Context Chat Backend behaviour in Nextcloud AIO

Hello,

I would like to continue the investigation from my previous topic:

:backhand_index_pointing_right: Nextcloud AIO becomes unresponsive even though all containers are healthy

because the recent behaviour seems related to the Context Chat / Context Chat Backend components.

Environment

  • Nextcloud AIO: 12.8.0 Beta

  • Nextcloud: 32.0.6 (AIO default)

  • OS: Ubuntu Server 24.04.3

  • Deployment: Docker (AIO)

  • Hardware:

    • 12 CPU threads

    • 16 GB RAM

    • NVMe storage

What happened after updating AIO

After upgrading to AIO 12.8.0 Beta and starting all containers:

  • a new Docker container containing context_chat_backend appeared automatically,

  • in Portainer the container was visible,

  • container state was running (green / healthy).

This was the first time I actually saw the backend container created automatically, which gave me the impression that the deployment process finally initialized correctly.

Attempt to initialize Context Chat again

I then enabled:

  • Nextcloud Assistant Context Chat – 5.3.1

However, inside Nextcloud Administration UI:

  • Context Chat Backend (5.3.0) still behaved as if it was not running,

  • despite the Docker container being visible and running externally.

context_chat_backend
context_chat_backend1905×677 159 KB

So the system state became inconsistent:

Component State
Docker container running
Nextcloud Admin UI backend not detected

Logs inspection

After checking logs (first context_chat_backend container after AIO start), multiple errors appeared related to the backend initialization.

context_chat_docker_log.odt (5,7 KB)

Because of this inconsistency I performed a clean retry:

  1. stopped and removed:

    • Nextcloud Assistant Context Chat

    • Context Chat Backend

  2. enabled Nextcloud Assistant Context Chat again to re-trigger initialization.

Current state

After reinstall attempt:

  • Context Chat Backend container is no longer created

  • In Apps → Disabled Apps I now see:

:backhand_index_pointing_right: Context Chat Backend – Heartbeat check failed

The deployment no longer progresses and no backend container appears anymore.

hearthbeat_check_fauled
hearthbeat_check_fauled1911×658 145 KB

Why I am posting this here

This is mainly a status report continuing the earlier instability investigation.

I am not trying to guess the root cause — I only want to document the observable behaviour because:

  • earlier AIO freezes described in the linked topic may have been connected to Nextcloud Assistant Context Chat & Context Chat Backend components,

  • deployment behaviour changed after upgrading to AIO 12.8.0 Beta,

  • backend container creation seems inconsistent between attempts.