More informative error messages when adding a federated participant fails
Open
Nobody has claimed this yet.
enhancement
feature: api 🛠️
feature: federation 🌐
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
I tired to open a chat with some external users. Sometimes that fails and the only, generic error is:
"Es ist ein Fehler beim Hinzufügen der Teilnehmer aufgetreten."
I tried to find out, why they failed.
- One instance restricted federated chats to certain domains. It worked, when we disabled that feature. So it works as intended. But it would be nice if Nextcloud instances were a bit more informative. It should say, that you are not allowed to add this user.
- One instance timed out.
- One instance was in maintainance mode.
The error message should say something like "Couldn't reach the other nextcloud. Make sure it is up an running." And then link to the cloud.
Nextcloud 29.0.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by locating the federated participant-add flow and tracing how domain restrictions, timeouts, and maintenance mode are reported. Done means these cases produce distinct informative messages, including a link to the other Nextcloud instance where appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100