Issue with Nextcloud Assistant AI Chat - No Response on Questions

ℹ️ Support
, ,
1

Hello,

I am using Nextcloud AIO version 12.5.0 with Nextcloud version 32.0.4 and Nextcloud Assistant version 2.12.0, integrated via a paid OpenAI API. However, I am encountering an issue with the Nextcloud Assistant Chat module. Whenever I input a question into the AI Chat, I do not receive any response. The system seems to be processing the question (as indicated by the “working” status), but no answer is returned.

nextcloud_AI_chat_loading_issue
nextcloud_AI_chat_loading_issue1202×821 38.3 KB

Interestingly, other modules such as Text Processing, Translation, Emoticon Generation, and Image Generation all work without issues, providing responses within seconds. Similarly, the Nextcloud Assistant Talk Bot is functioning correctly.

A few versions ago, everything was working fine, but now, since today, I can no longer get a response from the AI Chat.

I have already tried recreating all the containers, but the issue remains.

Has anyone encountered something similar, or can anyone suggest a fix for this?

2

Hello, I am having the same issue, does anyone found a solution for this ? it takes around 3-4mins for an answer, and when 2 or more users are using the AI chat at the same time none will work or have an answer.

3

I did some additional testing today and may have found something interesting.

I tested on the following setup:

  • Nextcloud AIO: 12.7.0 (stable)

  • Nextcloud: 32.0.6 Autumn

  • Nextcloud Assistant: 2.13.0

  • Nextcloud Context Agent: 2.3.0

After trying several different combinations, I discovered that Nextcloud Assistant Chat started working only after I disabled (not removed) the Nextcloud Context Agent.

Steps that worked for me:

  1. Disable Nextcloud Context Agent (the Docker container created by it shows the status stopped in Portainer).

  2. Test Nextcloud Assistant → AI Chat started working immediately.

  3. Re-enable Nextcloud Context Agent again.

  4. After re-enabling it, Nextcloud Assistant continued working normally.

So it seems the Nextcloud Context Agent may get stuck in some inconsistent state, and toggling it off/on resolves the issue.

I would appreciate it if someone else could confirm whether this workaround also fixes the problem on their setup.