Support intro
Sorry to hear you’re facing problems 
help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.
In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:
Or for longer, use three backticks above and below the code snippet:
longer
example
here
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can 
Some useful links to gather information about your Nextcloud Talk installation:
Information about Signaling server: /index.php/index.php/settings/admin/talk#signaling_server
Information about TURN server: /index.php/settings/admin/talk#turn_server
Information about STUN server: /index.php/settings/admin/talk#stun_server
Nextcloud version (eg, 24.0.1): 24.0.1
Talk Server version (eg, 14.0.2): spreed: 23.0.6
Custom Signaling server configured: yes — strukturag/nextcloud-spreed-signaling:2.1.1
Custom TURN server configured: yes — coturn (coturn/coturn:4.6-alpine)
Custom STUN server configured: yes — coturn (same instance)In case the web version of Nextcloud Talk is involved:
Operating system (eg, Windows/Ubuntu/…): not relevant
Browser name and version (eg, Chrome v101): not relevant
In case mobile Nextcloud Talk apps are involved:
Talk iOS version (eg, 14.0.2): not relevant / not invovled
Talk Android version (eg, 14.0.2): 24.0.1
Nextcloud version: 33.0.2
On WebSocket reconnect or renewed call attempt, the Talk Android app does not call participants/active before attempting to join a call room via joinRoom. This means it either reuses a stale room-session token or never mints one, and the join never progresses past registration. Server-side, the client registers successfully on the signaling server (hub.go:1064: Register user ...) but never sends a room-join or call-join request afterward. The call remains in a perpetual “incoming”/ringing state client-side, while the caller sees “waiting for others to join the call.” This matches the open upstream report: Call connection fails. ("code":"no_such_room","message":"The user is not invited to this room.") · Issue #3863 · nextcloud/talk-android · GitHub (filed April 2024, unresolved). In this session, the behavior was reproduced on two separate Android devices simultaneously (one on WiFi, one on cellular), ruling out network-path-specific causes (TURN/coturn config changes made no difference).
URL of github unresolved issue: " Call connection fails. ("code":"no_such_room","message":"The user is not invited to this room.") · Issue #3863 · nextcloud/talk-android · GitHub "
Is this the first time you’ve seen this error? (Y/N): N — reproduced repeatedly across multiple sessions on multiple devices.
Steps to replicate it:
-
Have an active Nextcloud Talk room
-
Initiate a call from another client (browser or Android).
-
On the receiving Android device(s), the call rings/shows “incoming.”
-
Tap to answer.
-
Observe: no
participants/activeAPI call is made (confirmed via server logs); the app registers on the signaling WebSocket but never sends a join-room/join-call request. The call hangs indefinitely on “incoming” with a spinner; the caller sees “waiting for others to join.” -
The output of your Nextcloud log in Admin > Logging or errors in nextcloud.log in /var/www/:
No participants/active entries found in the log for the reproduction window
(2026-07-02T19:50–19:59 UTC), confirming the endpoint was never called by
either Android client during the failed join attempts.
The output of your Apache/nginx/system log in /var/log/____:
hub.go:1064: Register user test2@nextcloud from 172.16.1.14 ... Nextcloud-Talk v24.0.1 (session N3DJzOOU...)
hub.go:1064: Register user <redacted>@nextcloud from 172.16.1.14 ... Nextcloud-Talk v24.0.1 (session rp5O_1qe...)
clientsession.go:520: Session VehVDwA_T... joined room 44bibbp8 with room session id ...
room.go:899: Session VehVDwA_T... joined call 44bibbp8
(Note: only the initiating/browser session progresses to joinRoom/joinCall.
Both Android sessions above register on the WebSocket and are never seen
again in the log for this call — no join-room, no join-call, no error.)
Your browser log if relevant (javascript console log, network log, etc.):
PASTE HERE