# Signaling Server recommendations **URL:** \ **Category:** đź’¬ Talk (spreed)\ **Created:** [May 7, 2019, 2:17pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798 "2019-05-07T14:17:17Z")\ **Posts on this page:** 20\ **Page:** 3
**Author:** ![nowatbuer](https://help.nextcloud.com/letter_avatar/nowatbuer/32/6_22734026db12803ebb3e059622ac3534.png) [@nowatbuer](https://help.nextcloud.com/u/nowatbuer)\ **Post date:** [May 21, 2020, 5:55pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/41 "2020-05-21T17:55:13Z")
Hello, I just upgraded to 19 RC 3 which contains talk 9.0.0-rc.1. On administration/talk I can add external signaling servers and it is recommended to use one if there are more than 4 participants. Is this still a requirement? From the announcement I expected this to be obsolete. ---
**Author:** ![anon71540698](https://help.nextcloud.com/letter_avatar/anon71540698/32/6_22734026db12803ebb3e059622ac3534.png) [@anon71540698](https://help.nextcloud.com/u/anon71540698)\ **Post date:** [May 21, 2020, 6:26pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/42 "2020-05-21T18:26:39Z")
Marketing-speak is Talk 9 can handle 5 to 10 video conference participants. If this is the discrepancy you are talking about, then it’s just because the docs haven’t been updated. If you need more than 10 people, you’ll need to install - now open-sourced! - signaling server > **[strukturag/nextcloud-spreed-signaling](https://github.com/strukturag/nextcloud-spreed-signaling)** > > Standalone signaling server for Nextcloud Talk. Contribute to strukturag/nextcloud-spreed-signaling development by creating an account on GitHub. ---
**Author:** ![Pisoko](https://help.nextcloud.com/user_avatar/help.nextcloud.com/pisoko/32/22884_2.png) [@Pisoko](https://help.nextcloud.com/u/Pisoko)\ **Post date:** [May 28, 2020, 9:35am UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/43 "2020-05-28T09:35:11Z")
Hmm I tried a lot but still have issues to make it work with my testcloud. Is there a good howto anywhere? It is a little bit challenging to set this up (signaling + janus + nats + coturn + proxy + firewall). My signaling is running but nextcloud talk has issues, even when everything is green in the settings. ![signal](https://help.nextcloud.com/uploads/default/original/3X/7/6/76941a8dcbb63f9035b9961dda7ca0b1f7a038a5.png) ![signal2](https://help.nextcloud.com/uploads/default/original/3X/4/c/4c71c97d2fcab2eb8c146dc5e109fb8444372790.png) ![signal3](https://help.nextcloud.com/uploads/default/original/3X/a/a/aa54acc505c29e6d9732e85e603d41638246a1c4.png) ---
**Author:** ![alfred](https://help.nextcloud.com/letter_avatar/alfred/32/6_22734026db12803ebb3e059622ac3534.png) [@alfred](https://help.nextcloud.com/u/alfred)\ **Post date:** [May 28, 2020, 5:12pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/44 "2020-05-28T17:12:42Z")
Maybe this one: [https://morph027.gitlab.io/blog/nextcloud-spreed-signaling/](https://morph027.gitlab.io/blog/nextcloud-spreed-signaling/) ---
**Author:** ![akr](https://help.nextcloud.com/letter_avatar/akr/32/6_22734026db12803ebb3e059622ac3534.png) [@akr](https://help.nextcloud.com/u/akr)\ **Post date:** [May 29, 2020, 6:20pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/45 "2020-05-29T18:20:05Z")
I have the same issue. Signaling server was compiled and configured according to [https://github.com/strukturag/nextcloud-spreed-signaling](https://github.com/strukturag/nextcloud-spreed-signaling) readme). It starts without problems, runs on its own host, is configured with secure websockets. curl -i https://[my-signaling-server]:8443/api/v1/welcome HTTP/1.1 200 OK Content-Type: application/json; charset=utf-8 Server: nextcloud-spreed-signaling/8d9c9cc1cd9aa1b18b1cbf8c0d7e8a8b6fbe9738 Date: Fri, 29 May 2020 17:31:23 GMT Content-Length: 94 {“nextcloud-spreed-signaling”:“Welcome”,“version”:“8d9c9cc1cd9aa1b18b1cbf8c0d7e8a8b6fbe9738”} Nextcloud configuration: wss://[my-signaling-server]:8443 But the communication with Nextcloud 18 fails. When I start the Talk app, the JS console logs the following errors: ``` talk.js?v=c3a127c1-3:116 WebSocket connection to 'wss://[my-signaling-server]:8443/spreed' failed: Unknown reason h.Standalone.connect @ talk.js?v=c3a127c1-3:116 (anonymous) @ talk.js?v=c3a127c1-3:116 talk.js?v=c3a127c1-3:116 Error Event {isTrusted: true, type: "error", target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …} (anonymous) @ talk.js?v=c3a127c1-3:116 error (async) h.Standalone.connect @ talk.js?v=c3a127c1-3:116 (anonymous) @ talk.js?v=c3a127c1-3:116 setTimeout (async) h.Standalone.reconnect @ talk.js?v=c3a127c1-3:116 (anonymous) @ talk.js?v=c3a127c1-3:116 error (async) h.Standalone.connect @ talk.js?v=c3a127c1-3:116 v @ talk.js?v=c3a127c1-3:116 createConnection @ talk.js?v=c3a127c1-3:116 (anonymous) @ talk.js?v=c3a127c1-3:239 Promise.then (async) (anonymous) @ talk.js?v=c3a127c1-3:239 (anonymous) @ talk.js?v=c3a127c1-3:239 c @ talk.js?v=c3a127c1-3:583 (anonymous) @ talk.js?v=c3a127c1-3:583 forEach.e. @ talk.js?v=c3a127c1-3:583 oe @ talk.js?v=c3a127c1-3:219 a @ talk.js?v=c3a127c1-3:219 (anonymous) @ talk.js?v=c3a127c1-3:219 (anonymous) @ talk.js?v=c3a127c1-3:219 he @ talk.js?v=c3a127c1-3:239 pe @ talk.js?v=c3a127c1-3:239 beforeMount @ talk.js?v=c3a127c1-3:1626 He @ talk.js?v=c3a127c1-3:27 Kt @ talk.js?v=c3a127c1-3:27 e @ talk.js?v=c3a127c1-3:27 Mn.$mount @ talk.js?v=c3a127c1-3:27 init @ talk.js?v=c3a127c1-3:27 (anonymous) @ talk.js?v=c3a127c1-3:27 l @ talk.js?v=c3a127c1-3:27 (anonymous) @ talk.js?v=c3a127c1-3:27 e._update @ talk.js?v=c3a127c1-3:27 r @ talk.js?v=c3a127c1-3:27 dn.get @ talk.js?v=c3a127c1-3:27 dn @ talk.js?v=c3a127c1-3:27 e @ talk.js?v=c3a127c1-3:27 Mn.$mount @ talk.js?v=c3a127c1-3:27 e._init @ talk.js?v=c3a127c1-3:27 Mn @ talk.js?v=c3a127c1-3:27 (anonymous) @ talk.js?v=c3a127c1-3:1650 n @ talk.js?v=c3a127c1-3:1 (anonymous) @ talk.js?v=c3a127c1-3:1 (anonymous) @ talk.js?v=c3a127c1-3:1 Show 11 more frames talk.js?v=c3a127c1-3:116 Reconnect in 1955.4251047645466 ``` signaling-server doesn’t log, just listens to [my-signaling-server:8443] Is there any additional documentation how to configure nginx, Nextcloud and this signaling server? Nextcloud 18.0.4 nginx 1.14.2 janus 0.10.0 nats 2.1.7 ---
**Author:** ![opkky](https://help.nextcloud.com/letter_avatar/opkky/32/6_22734026db12803ebb3e059622ac3534.png) [@opkky](https://help.nextcloud.com/u/opkky)\ **Post date:** [May 31, 2020, 7:20am UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/46 "2020-05-31T07:20:01Z")
Guys, I am very sorry but here are my 2 cents about Talk in NextCloud. If it is so complicated to make Talk working why not to use other ready services for Collaboration and just make integration with NextCloud. I am not a programmer but very much interested to integrate [https://linkchat.io](https://linkchat.io) to integrate with NextCloud. I contacted owner and he told that it can b easily done with WebHooks Is there anybody who can help or at least interested to do the same? PS. I am using NextCloud for many years in my projects. ---
**Author:** ![anon71540698](https://help.nextcloud.com/letter_avatar/anon71540698/32/6_22734026db12803ebb3e059622ac3534.png) [@anon71540698](https://help.nextcloud.com/u/anon71540698)\ **Post date:** [May 31, 2020, 1:11pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/47 "2020-05-31T13:11:06Z")
> [@opkky](#): > > If it is so complicated to make Talk working… It isn’t. Talk works fine for one to one video communication. If your version is up to date, it should (allegedly) do 5 to 10 participant video conference a breeze. If you want to accommodate people from behind NAT/Firewall - install a STUN/TURN server. > [@opkky](#): > > …why not to use other ready services for Collaboration and just make integration with NextCloud. And that’s already done > **[BigBlueButton Integration - Apps - App Store - Nextcloud](https://apps.nextcloud.com/apps/bbb)** > > The Nextcloud App Store - Upload your apps and install new apps onto your Nextcloud Nextcloud 19 will have another option - the high performance backend from Struktur > **[Talk 9 brings grid view, file editing, open sources Talk back-end - Nextcloud](https://nextcloud.com/blog/open-sourcing-talk-back-end-rc-of-talk-9-brings-lots-of-improvements/)** > > Today we announce the improvements coming in Nextcloud Talk 9. This includes the introduction of a grid view, easy sharing of files with drag and drop and build in viewing and editing of files and documents that will help teams be more productive.... Here is the point - video conferencing with 10+ people is complicated. It primarily revolves around feeding synced video/audio streams to each participant. If your system uses nothing but WebRTC, you - as a participant - must send your webcam stream to (N-1) participants and receive N of them. In other words, **doubling** the number of participants **quadruples** the bandwidth need. Add to that video compression, NAT traversing, stream encryption, etc. - it quickly becomes too much **for the client** … Hence, there will never be a install it and forget it video conference app for all use cases. Unless you have a contract with Nextcloud and ask them to do it for you… Over time there might be docker images will all the components - GO, NATS, Janus, TURN, etc. - built-in.But setting it up and making it work for the end user like Zoom or Teams will take work… ---
**Author:** ![opkky](https://help.nextcloud.com/letter_avatar/opkky/32/6_22734026db12803ebb3e059622ac3534.png) [@opkky](https://help.nextcloud.com/u/opkky)\ **Post date:** [May 31, 2020, 4:21pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/48 "2020-05-31T16:21:33Z")
> [@anon71540698](#): > > If your version is up to date, it should (allegedly) do 5 to 10 participant video conference a breeze. Thanks. Lets see, Nextcloud 19 release date is soon 🙂 It is something to test for me. ---
**Author:** ![anon71540698](https://help.nextcloud.com/letter_avatar/anon71540698/32/6_22734026db12803ebb3e059622ac3534.png) [@anon71540698](https://help.nextcloud.com/u/anon71540698)\ **Post date:** [June 1, 2020, 2:05am UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/49 "2020-06-01T02:05:23Z")
> [@opkky](#): > > …It is something to test for me. And please share your experience when you do. I’d be surprised if it does 10, but even 6-7-8 would be huge improvement over original… ---
**Author:** ![opkky](https://help.nextcloud.com/letter_avatar/opkky/32/6_22734026db12803ebb3e059622ac3534.png) [@opkky](https://help.nextcloud.com/u/opkky)\ **Post date:** [June 1, 2020, 7:56am UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/50 "2020-06-01T07:56:16Z")
I am also skeptical because Media Server is needed more than a Signalling one to increase amount of people in the room. Especially for mobile users. It can be traditional media server with transcoding or SFU. BigBlueButton is too heavy for the integration with NextCloud. Something more simple is needed, jitsi or Linkchat are more interesting, at least in my opinion. ---
**Author:** ![akr](https://help.nextcloud.com/letter_avatar/akr/32/6_22734026db12803ebb3e059622ac3534.png) [@akr](https://help.nextcloud.com/u/akr)\ **Post date:** [June 1, 2020, 1:53pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/51 "2020-06-01T13:53:16Z")
I managed to connect to the standalone signaling server from my browser. I had to adjust the nextcloud signaling configuration to: wss://[my-nextcloud-server]:8443/standalone-signaling and adjust the nginx configuration according to [https://docs.nginx.com/nginx/admin-guide/security-controls/securing-http-traffic-upstream/](https://docs.nginx.com/nginx/admin-guide/security-controls/securing-http-traffic-upstream/) Now clients can invite each other, but a video/audio connection is not yet established, unfortunately… debugging further… ---
**Author:** ![akr](https://help.nextcloud.com/letter_avatar/akr/32/6_22734026db12803ebb3e059622ac3534.png) [@akr](https://help.nextcloud.com/u/akr)\ **Post date:** [June 5, 2020, 8:06pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/52 "2020-06-05T20:06:05Z")
It works - except that it doesn’t work. 🤔 If I start a call from the desktop or iOS app, both parties are “waiting for others to join…”, or “waiting for to join call…” and the call is not established. During that phase, I see a lot of 400 BAD\_REQUEST in nginx access log, i.e. “GET /ocs/v2.php/apps/spreed/api/v1/signaling/74k8hk5g HTTP/2.0” 400 107 “-” “Mozilla/5.0 (iOS) Nextcloud-Talk v9.0.0”. WTF? I don’t see client connections in the nats server. Should I? This seems suspicious to me - hmmm. Might this be related to the nats server? There is not much information about nats in [https://github.com/strukturag/nextcloud-spreed-signaling](https://github.com/strukturag/nextcloud-spreed-signaling) … still trying to understand the big picture of the HPB. Any help is welcome. It looks like the other party is not getting the information that this party has joined the call and vice versa. ---
**Author:** ![Chartman123](https://help.nextcloud.com/user_avatar/help.nextcloud.com/chartman123/32/15034_2.png) [@Chartman123](https://help.nextcloud.com/u/Chartman123)\ **Post date:** [June 5, 2020, 9:30pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/53 "2020-06-05T21:30:32Z")
Do you also use a Janus gateway? I had some problems at first until I opened the UDP ports used by it. ---
**Author:** ![akr](https://help.nextcloud.com/letter_avatar/akr/32/6_22734026db12803ebb3e059622ac3534.png) [@akr](https://help.nextcloud.com/u/akr)\ **Post date:** [June 6, 2020, 10:10am UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/54 "2020-06-06T10:10:19Z")
I’m using janus, but I just configured the turn\_rest\_api\_key. I’ve switched to setting up turn\_server, \_port, \_type … but it didn’t help so far. I didn’t find the proper setup yet. It is more like try-and-error at the moment, as there aren’t complete tutorials, unfortunately. ---
**Author:** ![Marcelo\_Lopez\_Foresi](https://help.nextcloud.com/user_avatar/help.nextcloud.com/marcelo_lopez_foresi/32/25845_2.png) [@Marcelo\_Lopez\_Foresi](https://help.nextcloud.com/u/Marcelo_Lopez_Foresi)\ **Post date:** [June 6, 2020, 8:31pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/55 "2020-06-06T20:31:18Z")
Hey there. I finally got i t to work. I will make some tutorial in the near future. For now, i’ll tell you what i did. In my set up a have 2 vmware vms. One for nextcloud and the other for signaling. Both are running ubuntu 18.04. Initially i base my configurations in tow tutorials: - [https://github.com/strukturag/nextcloud-spreed-signaling](https://github.com/strukturag/nextcloud-spreed-signaling) - [https://morph027.gitlab.io/blog/nextcloud-spreed-signaling/](https://morph027.gitlab.io/blog/nextcloud-spreed-signaling/) I did not use caddy nor the .deb packages for janus. I compiled everything by hand. I struggle a bit with libnice. But cheking out the the branch _latest-release_ did the trick. Then i ran: ``` ./autogen.sh ./configure --prefix=/usr make && sudo make install ``` Once a i had everythin in place, i hardcoded the internal ips for the signaling server and nextcloud in each host file (nextcloud and signaling): ``` 10.1.1.1 nextcloud.example.com 10.1.1.2 signaling.example.com ``` I configured the RTP port range in janus (20000-40000), the min and max ports for coturn (49152-65535), and opened the folowing ports in my firewall (doin DNAT): - Janus: UDP: 20000-40000 - coturn: - - UDP 3478, 49152-65535 - - TCP 3478 - - SCTP: 3478 - Signaling: TCP 443 (through nginx). What i did not: - Configured the external ip in coturn nor janus. That’s only for 1:1 nat. - I did not use the udp endpoint for turn in the signaling configuration. Now everything works fine. ---
**Author:** ![markc](https://help.nextcloud.com/user_avatar/help.nextcloud.com/markc/32/131_2.png) [@markc](https://help.nextcloud.com/u/markc)\ **Post date:** [June 18, 2020, 5:28am UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/56 "2020-06-18T05:28:59Z")
> [@Marcelo\_Lopez\_Foresi](#): > > I will make some tutorial in the near future Perhaps you could post a link to your tutorial here so google can easily find it. Thanks and looking forward to it. ---
**Author:** ![khal\_Kharboutly](https://help.nextcloud.com/user_avatar/help.nextcloud.com/khal_kharboutly/32/23491_2.png) [@khal\_Kharboutly](https://help.nextcloud.com/u/khal_Kharboutly)\ **Post date:** [June 18, 2020, 11:12am UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/57 "2020-06-18T11:12:27Z")
> [@Marcelo\_Lopez\_Foresi](#): > > I will make some tutorial in the near future. For now that would be really great . thanks ---
**Author:** ![akr](https://help.nextcloud.com/letter_avatar/akr/32/6_22734026db12803ebb3e059622ac3534.png) [@akr](https://help.nextcloud.com/u/akr)\ **Post date:** [June 20, 2020, 8:47am UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/58 "2020-06-20T08:47:19Z")
The problem with those nginx 400 errors (see above) was a missing trailing slash in my proxy\_pass configuration. Aaaahrrg, my fault. The connection was established successfully after I’ve removed and re-installed the Nextcloud Talk app! I don’t know why but it solved the issue. Existing conversations in the Talk app didn’t establish connections, both sides were just waiting for each other to connect… Strange, but true. I’ve written some notes here: [Nextcloud Talk Signaling](http://www.kruthoff.org/?p=156) ---
**Author:** ![gr4ssi](https://help.nextcloud.com/letter_avatar/gr4ssi/32/6_22734026db12803ebb3e059622ac3534.png) [@gr4ssi](https://help.nextcloud.com/u/gr4ssi)\ **Post date:** [July 23, 2020, 11:18am UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/59 "2020-07-23T11:18:32Z")
There is a tutorial for Debian to be found here: > **[Signalisierungsserver für Nextcloud aufsetzen: How-To - Nichteinschalten.de](https://nichteinschalten.de/signalisierungsserver-fuer-nextcloud-aufsetzen-how-to/)** > > Vor kurzem wurde die Software zum Betrieb von Nextcloud Talk in größeren Nextcloudumgebungen als Open Source veröffentlicht: man braucht einen eigenen Signalisierungsserver, um mit mehreren parallel Leuten effektiv über Nextcloud Talk arbeiten zu... It’s in German, but pretty straight forward. ---
**Author:** ![david4](https://help.nextcloud.com/letter_avatar/david4/32/6_22734026db12803ebb3e059622ac3534.png) [@david4](https://help.nextcloud.com/u/david4)\ **Post date:** [November 15, 2020, 5:03pm UTC](https://help.nextcloud.com/t/signaling-server-recommendations/52798/60 "2020-11-15T17:03:12Z")
Hello, Thanks to all for your good job. I have try this tutorial : [https://morph027.gitlab.io/blog/nextcloud-spreed-signaling/](https://morph027.gitlab.io/blog/nextcloud-spreed-signaling/) and this one : [https://nichteinschalten.de/signalisierungsserver-fuer-nextcloud-aufsetzen-how-to/](https://nichteinschalten.de/signalisierungsserver-fuer-nextcloud-aufsetzen-how-to/) In the signaling configuration on nextcloud it seem to be ok, I have no message, contrary to Pisoko. The logs are ok. curl -i [http://127.0.0.1:8080/api/v1/welcome](http://127.0.0.1:8080/api/v1/welcome) HTTP/1.1 200 OK Content-Type: application/json; charset=utf-8 Server: nextcloud-spreed-signaling/9206a56113064b8e44b0de12d5128f8e88617679 Date: Sun, 15 Nov 2020 16:52:33 GMT Content-Length: 94 {“nextcloud-spreed-signaling”:“Welcome”,“version”:“9206a56113064b8e44b0de12d5128f8e88617679”} But when I launch the test client : /etc/nextcloud-spreed-signaling# ./bin/client -addr localhost:8080 2020-11-13 14:29:42.744255 I | Using a maximum of 4 CPUs 2020-11-13 14:29:42.746439 I | Backend server running on http://[IP]:33249 2020-11-13 14:29:42.747624 I | Connecting to [ws://localhost:8080/spreed] 2020-11-13 14:29:42.748099 I | Starting 100 clients 2020-11-13 14:29:42.962092 I | Clients created 2020-11-13 14:29:52.753822 I | Unsupported message type: {Id: Type:error Error:context deadline exceeded Hello: Bye: Room: Message: Control: Event:} 2020-11-13 14:29:52.755354 I | Unsupported message type: {Id: Type:error Error:context deadline exceeded Hello: Bye: Room: Message: Control: Event:} 2020-11-13 14:29:52.758737 I | Unsupported message type: {Id: Type:error Error:context deadline exceeded Hello: Bye: Room: Message: Control: Event:} a lot of time and after : 2020-11-13 14:29:52.929880 I | Unsupported message type: {Id: Type:error Error:Post “http://[IP]:33249/auth”: dial tcp [IP]:33249: i/o timeout Hello: Bye: Room: Message: Control: Event:} 2020-11-13 14:29:55.557264 I | Received bye: &{Reason:hello\_timeout} 2020-11-13 14:29:55.558455 I | Received bye: &{Reason:hello\_timeout} 2020-11-13 14:29:55.559967 I | Received bye: &{Reason:hello\_timeout} When I go on http://[IP]:33249, I have a 404 error. It is the same with the 2 tutorial and on this computer and in a VM. With nextcloud 19 up to date. Do you have any idea ? It is working ? Thanks in advance Have a good day. [Previous page](https://help.nextcloud.com/t/signaling-server-recommendations/52798.md?page=2) [Next page](https://help.nextcloud.com/t/signaling-server-recommendations/52798.md?page=4)