Talk can't connect to Spreed signaling server

[ibahnasy]

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:

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

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): `32.0.1`
Talk Server version (eg, 14.0.2): 22.0.2
Custom Signaling server configured: yes version: nextcloud-spreed-signaling version ed94aeacec2758f99439c7d230c1b6889eb3b84e/go1.24.0
Custom TURN server configured: yes
Custom STUN server configured: yes

The issue you are facing: Can’t connect to high performance backend running on port 4443

[scubamuc]

@ibahnasy

Can’t connect to high performance backend running on port 4443

your signalling service should be reachable via DNS with a FQDN and a valid certificate!

• WebRTC Signalling service like “Janus WebRTC server” or “Spreed WebRTC server” is required for calls and conversations with multiple participants. The signaling server is used to establish a WebSocket connection between the participants in the call. Without it, all participants would have to upload their own audio/video individually for each other participant causing connectivity issues.

• Examples: https://signal.yourdomain.tld, wss://signal.yourdomain.tld

• Quick install - Nextcloud Talk API documentation

• High Performance Backend for Talk on Nextcloud with Docker

[emma_rose77]

This problem usually shows up when Talk can’t reach the Spreed signaling server because something isn’t set up right. First, make sure the signaling server is actually running and that the URL in your config is correct.
Also check your firewall or reverse proxy, because if WebSockets are blocked, Talk won’t connect. After fixing any changes, restart both services and try again—most of the time it works after that.

[ibahnasy]

The Spreed server is listening on the public IP with valid SSL certificate.

Now I configured Talk to connect using the FQDN however I still get error “500”.

Even when I run tcpdump on port 4443 while testing the connection in Talk settings, I see no traffic.

[scubamuc]

@ibahnasy

Now I configured Talk to connect using the FQDN however I still get error “500”

if your reverse proxy for that FQDN pointing to signal.yourdomain.tld is configured correctly, the port number (:4443) is not required.

did you see this: High Performance Backend for Talk on Nextcloud with Docker with example and explanation?