Turn Server Test Returning "NO ICE candidates...."

ℹ️ Support
1

I host my Nextcloud instance on Docker.
When I initiate a call, it shows up with the notification that a Turn Server might be required for this process to work.

I have followed the steps provided in the official Nextcloud Talk API Documentation.
Yet it didn’t work.

I tried using a docker image for coturn with the same config as well, but that didn’t seem to work either.

Please Note : I have forwarded port 3478, 443, and 80 and have also allowed these ports through firewall.

Here’s my turnserver configuration :

listening-port=3478
fingerprint
lt-cred-mech
use-auth-secret
static-auth-secret=mykey
realm=mydomain.ml
total-quota=100
bps-capacity=0
stale-nonce=600
no-loopback-peers
no-multicast-peers

What am I missing here?

2

Were you adding the turn secret to the config page of the talk app at the admin settings of Nextcloud?

3

Yes I did that. And that is when the test showed “no ice candidates returned…”

4

What if you disable it?

you can add verbose as well to the config file

5

Okay I’ll try it and update you.

6

Tried it.
Still says the same

7

Is there any other method to try out?

9

listening-ip=XX.XX.XX.XXX

10

Oh okay. Should I add my public ip there?

12

If I remember correctly, there may also be some issues depending on the browser (client) you are using to check the turn server. Which browser are you using?

13

I tried with firefox as well as chrome

14

Did you try the following test？Trickle ICE

15

yes. I did the test. I uncommented the username and password and added my own to the conf file and tested it.
The output was “Not reachable?”

16

yes  

17

I added the public IP. When I restart the coturn service, it shows that the restart procedure failed
Here’s the output after running “journalctl -xe”

May 04 06:21:38 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.MKBSnD.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:21:44 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.yoN6dO.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:21:49 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.LZS8zt.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:21:54 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.AQ5m0D.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:21:59 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.yBNPPU.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:22:05 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.CuR0wk.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:22:10 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.4NEx74.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:22:15 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.Kx84Sn.mount: Succeeded.
░░ Subject: Unit succeeded
...skipping...
May 04 06:21:38 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.MKBSnD.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:21:44 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.yoN6dO.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:21:49 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.LZS8zt.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:21:54 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.AQ5m0D.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:21:59 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.yBNPPU.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:22:05 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.CuR0wk.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:22:10 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.4NEx74.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:22:15 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.Kx84Sn.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:22:18 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-27d58c27782c11ebd111f0646473d9b128eee5ea8d619f582e8d2a40277994f3-runc.rP30tn.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:22:20 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.VolvGA.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
May 04 06:22:22 starbetaserver sudo[619116]: pam_unix(sudo:session): session closed for user root
May 04 06:22:26 starbetaserver systemd[610839]: run-docker-runtime\x2drunc-moby-a2b2ea11ef4d0defcfa6e5baad2d80bd482fc6d91054aae20e4bcb32c5c12548-runc.Sbk91y.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit UNIT has successfully entered the 'dead' state.
18

Looks like that it does not work with your docker image. I am not using it and everything works fine.

19

Mm. I’m not sure why. But nextcloud is weird sometimes.

I can connect to some calls. But most of them seem to show the same turnserver notification.

20

Is there any other way to tackle this issue ?

21

Did you fill in the STUN server in the admin panel of Nextcloud as well?

22

That was filled in by default