Dynamische IP? Port in FB weitergeleitet? Coturn installiert?
a) Statische IP
b) Weiterleitung FB eingerichtet
c) Coturn installiert
und auch noch d) Nextcloud Talk Einstellungstest URL;secret;TCP funktioniert und wird im coturn Log protokolliert.
Oh sorry, dachte eins davon würde mir einen Hinweis geben wo anzusetzen, leider kann ich nicht weiterhelfen, keine Idee.
Thank you for clarification. So in theory I should only need to forward 3478. Unfortunately I can’t do the testing of one port vs two ports as my problem was solved by client’s browser change (he used to use Firefox, it used to work fine, and yesterday he had a problem, he tried Chrome and it worked…) I know, the possible need for TURN should only depend on how he is connected to WAN and not on his browser, but this did actually happen…
I’d kindly like to remind you that this is an international forum where we agreed to use the English language for communication.
So please don’t capture an english thread and answer in your native language (you could do that in the referring subforum)… this would be considered as highly impolite. And - remember - we do want to treat each other here polite and friendly
Thanks for your understanding.
FWIW, in case anyone happens to be interested in an alternative to Coturn: eturnal should be compatible with Nextcloud Talk as well.
great what are the benefits over coturn ?
eturnal doesn’t really offer notable features above Coturn (yet). Quite the opposite: While Coturn implements all features under the sun (including lots of old cruft that’s no longer in use), eturnal is a minimalistic server that implements just those that are actually used by apps such as Talk. So it might be (even) more straightforward to set up, esp. on distributions that don’t offer a Coturn package (there’s no dependencies, you basically just extract the binary tarball, configure the shared secret, and start the systemd service). And as it’s written in Erlang, it avoids a class of security-related issues Coturn ran into again just recently.
That said, I think Coturn is totally fine for most users
Many thanks for sharing. I was always wondering if there were any other TURN servers, but didn’t find any so far .
Yes while Coturn should be generally fine, it good to have alternatives also in terms of competitive or simply for simpler use cases.
Binaries are btw only available for x86_64 systems, while ARM users need to compile themselves, as long as there is no 3rd party or distro repo providing such.
… ah it’s actively coded by you in person and just three days released. ProcessOne/ejabberd to give some association. Lets see if this is something to replace Coturn in our DietPi Nextcloud Talk integration where we aim to go lightweight where possible. I would need to build binaries + dpkg/deb packages for armv6hf (RPi) armv7hf and arm64 and would simply create those for x64_64 as well. Might be nice for others as well to give it a (quicker) try, when not being to experienced with source builds.
Cool! If you decide to look into it and stumble over anything, feel free to ping me by email (firstname.lastname@example.org). I was thinking about offering ARM binaries myself, but have no system for building those and am still unsure whether I want to go for cross-compiling.
Just wanted to inform you about this:
Because Nextcloud use PHP, I had hoped someone writes a TURN server in PHP so every Nextcloud Installation could use it.
After update to Ubuntu 20.04 and Nexcloud 20.0.1 i got an ICE server Error. No working ICE candidat
Under Ubuntu 19.04 and Nextcloud 18 and 19.x it works very well.
Thanks for this how-to. Everything went well installing the coturn server (on Debian 10)
And here are the status :
● coturn.service - coTURN STUN/TURN Server Loaded: loaded (/lib/systemd/system/coturn.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-12-04 10:57:09 UTC; 24min ago Docs: man:coturn(1) man:turnadmin(1) man:turnserver(1) Process: 25469 ExecStart=/usr/bin/turnserver --daemon -c /etc/turnserver.conf --pidfile /run/turnserver/turnserv Process: 25471 ExecStartPost=/bin/sleep 2 (code=exited, status=0/SUCCESS) Main PID: 25470 (turnserver) Tasks: 9 (limit: 4915) Memory: 5.5M CGroup: /system.slice/coturn.service └─25470 /usr/bin/turnserver --daemon -c /etc/turnserver.conf --pidfile /run/turnserver/turnserver.pid
Dec 04 10:57:07 mydomain.tld turnserver: 0: IO method (general relay thread): epoll (with changelist) Dec 04 10:57:07 mydomain.tld turnserver: 0: turn server id=2 created Dec 04 10:57:07 mydomain.tld turnserver: 0: IO method (general relay thread): epoll (with changelist) Dec 04 10:57:07 mydomain.tld turnserver: 0: turn server id=3 created Dec 04 10:57:07 mydomain.tld turnserver: 0: Total General servers: 4 Dec 04 10:57:07 mydomain.tld turnserver: 0: IO method (auth thread): epoll (with changelist) Dec 04 10:57:07 mydomain.tld turnserver: 0: IO method (auth thread): epoll (with changelist) Dec 04 10:57:07 mydomain.tld turnserver: 0: IO method (admin thread): epoll (with changelist) Dec 04 10:57:07 mydomain.tld turnserver: 0: SQLite DB connection success: /var/lib/turn/turndb Dec 04 10:57:09 mydomain.tld systemd: Started coTURN STUN/TURN Server.
But when I add the TURN server URL, with the port on 3478 or 5349 + the secret phrase in the Nextcloud admin page I got a “no working ice candidates returned by the turn server” error.
My Nextcloud is 19.0.3.
Tks for your ideas.
Was just reading a German thread and apparently if you change the browser and test it with Chrome instead of, like in my case, Safari, the test will be succesful. Don’t ask me what the heck can be wrong about Safari, but I tried this and it’s actually true.
follow step by step but get error when testing server
“Error: No working ICE candidates returned by the TURN server”
Double-check your authentication secret: Talk / Turnserver self test - #2 by anon93002831
Otherwise check you coturn logs.
EDIT: Just read the posts above yours: Some browsers seem to show a wrong result. Not sure why the browser should be involved at all, but if you don’t see any errors in the coturn logs, try it with a different browser.
If this is with the very last NC21/Talk11, it is likely meaningless
The latest (minor) update Talk 11.2.2 fixes the error message: it now properly qualifies valid TURN servers (coTURN in my case)…
This would be great. Until now i have only found https://www.reddit.com/r/NextCloud/comments/fxowmg/looking_for_docker_stack_with_nextcloudturnstun/ and it is really insufficiently documented.