nextcloud / nextcloud/spreed

Requests to HPB service sometimes can't be validated / accounts marked "expired"

Open
#16,227 5 comments 0 reactions 1 assignee View on GitHub

@fancycode is already working on this.

Since Oct 29, 2025.

bug Needs triage
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Sometimes it happens that a request to the HPB service to update the account properties can not be validated by the HPB service (https://github.com/nextcloud/spreed/blob/0526b72b8fae3164c252d9d044a9a85d47f1a520/lib/Controller/HostedSignalingServerController.php#L62). If this happens the HPB service request returns a 401 Unauthorized which causes the account to be marked as "expired". This causes confusion with customers that see a notification about the expired account (that still can be used successfully).

While it's a bug that the validation fails, also accounts should not be marked as "expired" then.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.