nextcloud / nextcloud/nextcloud-talk-recording
[0.30] upload recording fails with 401
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- Python
- Stars
- 34
- Forks
- 16
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 4
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.
Steps to reproduce
- Record a meeting / Stop the Recording
- No notification of the completed upload
- Recording is not being uploaded. However, you can find it in /tmp of the recording server
Expected behaviour
Recording should be uploaded to nextcloud instance.
Actual behaviour
Upload process fails with:
2026-09-05T10:24:26.596482+02:00 rec nextcloud-talk-recording[7223]: requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://domain.de/public.php/dav/uploads/zrAbAGc6AZykG9c/F_vNn99IWo-9CCmejv7Ng8aXog_vSgYxdhpL0MMTw4U
Server configuration
Web server: Apache
Database: MySQL
PHP version: 8.4
Nextcloud version: 34.0.3
Is the problem perhaps related to https://github.com/nextcloud/server/issues/59391 ?
cheers!
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
Start by reproducing the recording upload from the recording server and trace the request to the Nextcloud public DAV upload endpoint shown in the error. Check the upload process and its authentication context, then verify that a stopped recording uploads successfully and no longer remains only in /tmp.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, mysql, php, python
- Domain
- authentication, backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100