Talk calls do not connect with signalling server configured

ℹ️ Support 💬 Talk (spreed)
, , , ,
1
Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

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:

example

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 :heart:

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): 31.0.14
Talk Server version (eg, 14.0.2): 21.1.9
Custom Signaling server configured: yes 2.1.0~docker
Custom TURN server configured: yes - stun.nextcloud.com:443
Custom STUN server configured: yes - personal one, works with XMPP

In case the web version of Nextcloud Talk is involved:
Operating system (eg, Windows/Ubuntu/…): Debian Stable
Browser name and version (eg, Chrome v101): Firefox 147

In case mobile Nextcloud Talk apps are involved:
Talk iOS version (eg, 14.0.2):
Talk Android version (eg, 14.0.2): 23.0.0

The issue you are facing: Calls connect fine without signalling server configured, but do not connect once it is configured.

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

  1. Enable signalling server

  2. Start call

  3. Answer call

  4. Stuck in infinite loop

  5. Disable signalling server

  6. Start call

  7. Answer call

  8. Connects immediately

The output of your Nextcloud log in Admin > Logging or errors in nextcloud.log in /var/www/:

https://forge.anderdonau.de/blindcoder/nextcloud-logs/src/branch/main/nextcloud_debug.log

The output of your Apache/nginx/system log in /var/log/____:

https://forge.anderdonau.de/blindcoder/nextcloud-logs/src/branch/main/nextcloud_apache.log

Your browser log if relevant (javascript console log, network log, etc.):

Not sure what's needed here
2

Some more information as that might help diagnosing:

Nextcloud is installed in an apache webserver running mod_php, in a LXC on proxmox with a public IPv4 address. That server hosts many applications, like other websites, mailserver, jabber server, also coturn for TURN.

Next to that LXC is another LXC which hosts docker containers maintained through portainer. In that second LXC I run nextcloud/aio-talk which the nextcloud instance from the first LXC connects to.

The docker container is fronted by the webserver that’s also hosting nextcloud acting as a reverse proxy:

	ProxyPass "/standalone-signaling/"  "http://172.20.1.25:8081/" upgrade=websocket
	#ProxyPassReverse "/standalone-signaling/"  "https://172.20.1.25:8081/" 
	RequestHeader set X-Real-IP %{REMOTE_ADDR}s
	RequestHeader set X-Forwarded-Proto expr=%{REQUEST_SCHEME}

Configuration in Admin → Talk is:

HPB-Backend URL: wss://cloud.anderdonau.de/standalone-signaling/ (green checkmark)

Shared secret double and triple checked.

TURN server is configured as well, tried tcp+udp (udp ports 3478 and 49xxx-65xxx and tcp 3478 allowlisted).

No recording and no SIP backend configured.

3

Narrowed it down a bit more.

I have now moved the AIO-Talk container from docker inside LXC inside Proxmox directly to Docker on the Proxmox host and exposed its own TURN server.

With that configured it works correctly. So I guess the issue is somewhere between the HPB and my coturn installation.

1 Like