nextcloud / nextcloud/talk-android
Http 400 Bad Request
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce
I have Nextcloud 32.0.2 addon on Homeassistant OS. Ssl is on. Https has 8099 port. Http has 8096 port. On chrome browser all ok.
Expected behaviour
Browser will be must run to login
Actual behaviour
Snapshots
Device brand and model
Samsung s10+ Snapdragon
Android version
10
Nextcloud Talk app version
22.0.2
Nextcloud server version
32.0.2
Talk version
No response
Custom Signaling server configured
None
Custom TURN server configured
None
Custom STUN server configured
None
Android logs
No response
Server log
192.168.68.109 - - [24/Nov/2025:10:47:59 +0300] "GET /status.php/status.php HTTP/1.1" 400 248 "-" "Mozilla/5.0 (Android) Nextcloud-Talk v22.0.2"
192.168.68.109 - - [24/Nov/2025:10:47:59 +0300] "GET /status.php/status.php HTTP/1.1" 400 248 "-" "Mozilla/5.0 (Android) Nextcloud-Talk v22.0.2"
Additional information
No response
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 with the server log and trace the Android Talk request that produces GET /status.php/status.php against the stated Home Assistant and Nextcloud setup. Reproduce the login attempt and collect Android logs; done means the request path is corrected and login succeeds without the HTTP 400 response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100