Coturn: TURN Server in Docker installieren
Ich brauchte kürzlich für ein Update einen funktionierenden TURN Server. Ohne den lief das neue Feature schlicht nicht. Meine erste Idee war bequem. Öffentlichen TURN Server nehmen, fertig. Kostenlose Basisversion, 20 GB Traffic im Monat, klang ausreichend.
War es nicht.
Ich hatte Verb...
https://www.cleveradmin.de/blog/2026/03/eigenen-coturn-turn-server-mit-docker-installieren/
#Allgemein #coturn #docker #netzwerk #selfhosting #webrtc
RE: https://infosec.exchange/@enablesecurity/116130697375709804
Published the "how to fix it" companion to our TURN security threats post. Best practices guide + coturn config templates at three security levels.
Also discussing TURN security on WebRTC Live today: https://webrtc.ventures/webrtc-live/
https://www.enablesecurity.com/blog/turn-security-best-practices/
https://www.enablesecurity.com/blog/coturn-security-configuration-guide/
Two weeks ago we published our analysis of TURN security threats. Today: how to fix them.
New guides covering implementation-agnostic best practices (IP range blocking, protocol hardening, rate limiting, deployment patterns) and coturn-specific configuration with copy-paste templates at three security levels.
Best practices: https://www.enablesecurity.com/blog/turn-security-best-practices/
coturn guide: https://www.enablesecurity.com/blog/coturn-security-configuration-guide/
Config templates on GitHub: https://github.com/EnableSecurity/coturn-secure-config
coturn 4.9.0 dropped yesterday with fixes for CVE-2026-27624 (IPv4-mapped IPv6 bypass of deny rules) and an inverted web admin password check that had been broken since ~2019. The guides cover workarounds for older versions.
#infosec #webrtc #security #TURN #coturn #penetrationtesting #voip #serversecurity
重新配置自托管了simplex，踩了一点坑，但是终究是配置好了（
部署SMP服务器：https://simplex.chat/docs/server.html
部署XFTP服务器：https://simplex.chat/docs/xftp-server.html
部署WebRTC服务器：https://simplex.chat/docs/webrtc.html
测试WebRTC ICE服务器：https://icetest.info
客户端下载页面：https://simplex.chat/downloads/
Few days ago I successfully configured #coturn to have a TURN/STUN server for in-family calls. But … looks like bots or some bad guys constantly trying to connect to my TURN server to use it for something :-(
Of course, it is impossible, since anonymous access or any other access without right key is impossible. But, there are no IPs of attackers in the log file, even wth "Verbose" directive — only my local and public IPs and my server's hostname :drgn_cry:
Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?
So, der prosody #xmpp server läuft mit #coturn für Voice und Video, allen Features passen und wir haben 100% Compliance. Yay.
Mal sehen, was es jetzt wieder für einen Kampf wird, vom Test- auf den Prodserver umzuziehen.
Das letzte Zahnrad für die digitale Unabhängigkeit … #selfhosting
Got #prosody running and also established #coturn for stun/turn on the test server. It looks pretty good and is very lightweight, and #conversations looks like a decent client. happy so far...
But compared to #matrix, the huge amount of features and XEPs is a different story.
Question de noob:
Le multipath TCP ca a un interet pour les transitions entre connexions 5g/wifi les apps voip? Genre une app android #conversations qui communique en vers un service relai #coturn ?
Je crois que la voip utilise UDP en general.
Somebody out there who has a working setup with a webserver and a turnserver running both on port 443 tcp? And is willing to share the anonymized configs? Spent several hours but didn't succeed 😭
#nginx #coturn #turnserver #webserver #haproxy
The #Ansible role for #BigBlueButton is now able to install and configure BBB 3.0.x with embedded #coturn, even on cloud VMs behind a NAT router or firewall.
https://github.com/ebbba-org/ansible-role-bigbluebutton/tree/bbb/3.0
i have been meaning to open source this for awhile and why not today.
https://codeberg.org/CobyPear/up-down
i wrote a little bit about the coturn portion of things here but i never got back to this so i figured it is time to share it.
i used it to successfully collaborate with a friend across the country and we sent each other .wav files back and forth and pasted them together into an album.
we did test the live jam room and it worked (even via mobile), however i was never able to do a live jam session over it due to schedule constraints but lmk if you make that happen.
if you have questions ask them here or open an issue. no promises :)
tbh not sure it would still work today out of the box, but it should! it uses old versions of things of course.
#oss #opensource #coturn #scrappyfiddles #sveltekit
WebRTC debugging.
I spent hours debugging and now need to share the solution with the world.
Tried to establish a #WebRTC-based #p2p connection (using #yjs and y-webrtc) in a LAN behind NAT, but ICE failed. Neither STUN nor TURN seemed to help, nor did a local #Coturn or local signaling server.
The solution was to force TURN through TCP, i.e. using something like this as TURN id:
turn:ADDR:PORT?transport=tcp
Kudos for the final hint and other debugging pointers:
What would make my #coturn server work with #Nextcloud talk but not with #matrix synapse or any of the matrix clients. I have used the same settings for both.
Any help would be appreciated by the #OpenSource community :)
Tux Flash: coturn, STUN, TURN, KI-Bild/Textgeneratoren, Cosmic-Desktop, Mail
https://tube.tchncs.de/videos/watch/19288700-9c35-4170-86c3-8375edc2f8fb
Can any anyone suggest some tools for diagnosing poorly functioning Matrix audio/video calls?
Right now I don't even know whether I should be filing bugs on Matrix or Element or Yunohost or Coturn or Synapse, and I'm really hoping to give some more useful info than "Calls often don't connect and even when they do they're often missing either video or audio." 🤔
Thanks!
Not at all... *THANK YOU* for your unsolicited advice! Why yes, my setup *does* use coturn, and I happen to know it does *not* resolve #IPV6, however I figured that wasn't important if the domains and server were all configured using IPV4. My knowledge here is very limited, so... is that likely an issue?
I'm *very* heartened there may be a known way out of this mess! Now to look up how complicated the fixes are for my @yunohost setup...
Irgendjemand eine Idee, wie man realisieren kann, dass User im lokalen Netzwerk über coturn mit Usern außerhalb des lokalen Netzwerks miteinander callen können? Wenn beide im lokalen Netz sind, gehts. Wenn beide außerhalb sind auch. Nur die Kombination geht nicht. Habe keine Idee, wie ich die Route bauen kann oder eine Firewallregel hinzufügen muss, dass das geht. #coturn
