nextcloud / nextcloud/context_chat_backend

Error received from Context Chat Backend (ExApp) with status code 500

Open
#281 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug priority: normal
Dominant language
Python
Stars
27
Forks
24
Avg merge
3d 4h
Merged PRs (30d)
6

Description

Which version of Nextcloud are you using?

Nextcloud Hub 25 Autumn (32.0.5)

Which version of PHP context_chat are you using?

5.3.1

Which version of backend context_chat are you using?

5.3.0

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Edge:latest

Nextcloud deployment method?

AIO

Describe the Bug

Running context_chat:scan lists a few files and then errors out with:

In LangRopeService.php line 168:

Error received from Context Chat Backend (ExApp) with status code 500: Embedding Request Error: Error: failed to connect
to the embedding service

To Reproduce

I already had Nextcloud AIO, the appengine and AI assistant sewtup and working when context chat was released. Installed that and it has been stuck at the "initial indexing" hasn't finished since install (months ago). When I use occ to try and run the scan command manually I get the above error.

PHP logs (Warning these might contain sensitive information)

No response

Ex-App logs (Warning these might contain sensitive information)

No response

Server logs (if applicable)

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with LangRopeService.php at line 168 and reproduce the failure using context_chat:scan. Review the available PHP, Ex-App, and server logs around the 500 response and the embedding service connection. Done means identifying why the embedding request cannot connect and confirming that initial indexing completes.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, python
Domain
ai, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.