Fail to install and configure Nextcloud Signaling + Coturn

Support apps
, , , ,
1

What app is this about, and its version: Nextcloud Signaling 2.1.1~ynh1
What YunoHost version are you running: 12.1.40.1
What type of hardware are you using: Old laptop or computer

Describe your issue

Hi,

I installed CoTurn, and then i installed Nextcloud Signaling, but it’s not working (i can’t make video-conference with people outside my network).

Note about the installation of Nextcloud Signaling:
I had to use the ‘pwd__YOUR_DOMAIN’ instead of the “shared secret”.
Using the “shared secret” i can’t create a conv.

Using the “pwd__YOUR_DOMAIN"i can create conversation.

See this ticket: Bug report: Generated HPB passwords are not visible in the YunoHost interface · Issue #14 · YunoHost-Apps/nextcloud-signaling_ynh · GitHub

Also, i needed to open the 5349 port both in TCP & UDP (i found this by running YNH Diag, because the coturn postinstall doesn’t say anything about opening a special port)

Maybe i missed something: Do i need to install the CoTurn server on a different machine? (right now, i have 3 soft on the same machine: YNH with NC+NC Signaling+CoTurn)

Share relevant logs or error messages

Running the Coturn test from here: Trickle ICE , i got this error
The server turn:coturn.mydomain.tld:5349 returned an error with code=401

Log CoTurn: hastebin
Log Janus: hastebin
Log Nats-server: hastebin
Log Nextcloud Signaling: hastebin

2

Seeing this post: Installer generated user and password doesn't work. · Issue #43 · YunoHost-Apps/coturn_ynh · GitHub ,

  1. I disable auth from /etc/turnserver.conf and enable no-auth (commenting user and password, and adding no-auth).
  2. Then testing again with Trickle ICE , i got this new error: The server turn:coturn.mydomain.tld:5349 returned an error with code=701:
3

Seeing this commit (created by the one who packaged Nextcloud Signaling): Enh udp 443 by zamentur · Pull Request #31 · YunoHost-Apps/coturn_ynh · GitHub

  1. i create this file:
    sudo nano /etc/yunohost/hooks.d/post_iptable_rules/60-coturn
  2. and i add this inside:
    #!/bin/bash
    iptables -t nat -A PREROUTING -p UDP --dport 443 -j REDIRECT --to-ports 5349
  3. then i reload my firewall: sudo yunohost firewall reload

Testing from trickle ICE i still have this error: The server turn:coturn.mydomain.tld:5349 returned an error with code=701:
Testing from nextcloud talk: i can’t connect to someone outside my local network

4

testing from Trickle ICE , all of this test return the same error: “returned an error with code=701:”

  • turn:coturn.mydomain.tld:5349
  • turn:coturn.mydomain.tld:443
  • turn:coturn.mydomain.tld:443?transport=udp

It seems that the problem come from Coturn.

Anyone has an idea on how to configure Coturn?

[Nextcloud-signaling] Video conference with Nextcloud Talk
5

It seems that many people are having this problem with the CoTurn configuration: The server returned an error with code=701: STUN/TURN allocate request timed out. · Issue #678 · coturn/coturn · GitHub
But even reading their solution, i can’t manage to make Coturn working….

And i’m not the only one lost on this problem on this forum:

Anyone succeed to configure CoTurn?

6

Hello,

Error 701 indicates an authentication problem.

After several attempts, I’ve finally succeeded to use Nextcloud Signaling. Work only on port 5350 (http), not on 5351. Make sure your firewall configuration and box redirection are consistent with that. In contradiction with some documentation, do not use port 443, as it’s already used for another services.

In Nextcloud Signaling configuration page, report and adapt the information from Coturn configuration page :

  • TURN server terminal point : turn:coturn.yourdomain.com:5350?transport=udp,turn:coturn.yourdomain.com:5350?transport=tcp (‘turn:coturn.yourdomain.com:5350’ is from coturn configuration page)
  • TURN secret : yourTURNsecret (same origin)

Once NS is installed and configured, click on “view secrets”. In history drop-down window, you should be able to read login data you will need to enter in Nextcloud Talk configuration page (an address and a secret). If not, secret can be found in /etc/yunohost/apps/nextcloud-signaling/settings.yml , at pwd__your_cloud_domain: yourSIGNaLinGsecret

In Nextcloud Talk configuration page:

  • High Performance backend:

    • URL : wss://thedomainyouinstallednextcloudsignaling/standalone-signaling
    • shared secret : yourSIGNaLinGsecret
    • if correct, configuration page display some server information and say “OK” with a geen check

  • STUN server :

  • TURN server :

Check also in Yunohost configuration if all services are up, especially COTURN.

PLX

7

Thanks plx, adding the turn server configuration directly in Nextcloud Talk parameter was the solution!

I thought it wasn’t necessary because the Talk HPB (High performance Backend) = Nextcloud Signaling was already connected to coturn

I tested:

  • configuring only the Talk High Perfomance Backend (and not the turn server) → it does not work
  • Configure only the turn server → it work but badly
  • Configuring both (HPB + Turn server) → it works well
8

I made a tutorial to explain all steps: Guide to install Nextcloud Signaling (High performance Backend) + CoTurn

1 Like
9

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.