#coturn — Public Fediverse posts

Well today I found out that coturn does NOT use /etc/coturn/coturn.conf but actually /etc/turnserver.conf 😅

I poured hours and hours in getting stuff to work and it turns out that I was editing the wrong file for this service the whole time... (the nextcloud interface only checks if the server is running and not whether the credentials you give it actually work)

In other news nextcloud talk is finally working XD
(though I get the same errors from the signaling backend as before)

#sysadmin #coturn #turnServer #nextcloud #nextcloutTalk

Well today I found out that coturn does NOT use /etc/coturn/coturn.conf but actually /etc/turnserver.conf 😅

I poured hours and hours in getting stuff to work and it turns out that I was editing the wrong file for this service the whole time... (the nextcloud interface only checks if the server is running and not whether the credentials you give it actually work)

In other news nextcloud talk is finally working XD
(though I get the same errors from the signaling backend as before)

#sysadmin #coturn #turnServer #nextcloud #nextcloutTalk

Well today I found out that coturn does NOT use /etc/coturn/coturn.conf but actually /etc/turnserver.conf 😅

I poured hours and hours in getting stuff to work and it turns out that I was editing the wrong file for this service the whole time... (the nextcloud interface only checks if the server is running and not whether the credentials you give it actually work)

In other news nextcloud talk is finally working XD
(though I get the same errors from the signaling backend as before)

#sysadmin #coturn #turnServer #nextcloud #nextcloutTalk

Well today I found out that coturn does NOT use /etc/coturn/coturn.conf but actually /etc/turnserver.conf 😅

I poured hours and hours in getting stuff to work and it turns out that I was editing the wrong file for this service the whole time... (the nextcloud interface only checks if the server is running and not whether the credentials you give it actually work)

In other news nextcloud talk is finally working XD
(though I get the same errors from the signaling backend as before)

#sysadmin #coturn #turnServer #nextcloud #nextcloutTalk

If anyone wants to build a [Matrix] stack, I’ve made a working stack publicly available. Feedback and contributions are welcome.

https://github.com/nean-and-i/matrix-stack

#DigitalSovereignty #DIDit #Matrix #Tuwunel #Caddy #LiveKit #Coturn

Is there a way to configure #Coturn like this?

#WebRTC #Linux #HomeAssistant

Is there a way to configure #Coturn like this?

#WebRTC #Linux #HomeAssistant

Is there a way to configure #Coturn like this?

#WebRTC #Linux #HomeAssistant

Is there a way to configure #Coturn like this?

#WebRTC #Linux #HomeAssistant

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/

#infosec #webrtc #security #TURN #coturn #voip

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/

#infosec #webrtc #security #TURN #coturn #voip

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/

#infosec #webrtc #security #TURN #coturn #voip

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/

#infosec #webrtc #security #TURN #coturn #voip

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

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

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

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

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

https://simplex.chat

重新配置自托管了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/

#simplex #coturn #selfhosting

https://simplex.chat

重新配置自托管了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/

#simplex #coturn #selfhosting

https://simplex.chat

重新配置自托管了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/

#simplex #coturn #selfhosting

https://simplex.chat

重新配置自托管了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/

#simplex #coturn #selfhosting

The following hashtags are trending across South African Mastodon instances:

#deltachat
#xmpp
#ejabberd
#selfhosting
#foss
#Today
#dovecot
#chatmail
#coturn
#polls

Based on recent posts made by non-automated accounts. Posts with more boosts, favourites, and replies are weighted higher.

The following hashtags are trending across South African Mastodon instances:

#deltachat
#xmpp
#ejabberd
#selfhosting
#foss
#Today
#dovecot
#chatmail
#coturn
#polls

Based on recent posts made by non-automated accounts. Posts with more boosts, favourites, and replies are weighted higher.

The following hashtags are trending across South African Mastodon instances:

#ejabberd
#selfhosting
#coturn
#southafrica
#limpopo
#schoolsafety
#saaf
#southafricanairforce
#aviation
#gripen

Based on recent posts made by non-automated accounts. Posts with more boosts, favourites, and replies are weighted higher.

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?

#TURN #STUN #selfhosting #networking #AskFedi

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?

#TURN #STUN #selfhosting #networking #AskFedi

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?

#TURN #STUN #selfhosting #networking #AskFedi

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?

#TURN #STUN #selfhosting #networking #AskFedi

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?

#TURN #STUN #selfhosting #networking #AskFedi

Just tested my Prosody server against the compliance checker at https://compliance.conversations.im My Prosody server got itself a 100% compliance rating, with in-band registration being disabled as it's more of a personal server than a public one, even with that public conference. If you want to see the results for yourself, check out https://compliance.conversations.im/server/simplygregario.us/ I will also point out that both Prosody and CoTurn (which provides media relay services for Prosody) are configured to be dual-stack, meaning everything works both on IPv4 and IPv6. Even got all 8 SRV records configured in DNS so CoTurn's STUN and TURN implementations will hopefully work flawlessly, both via TCP & UDP (and the TLS-based option is included). #Prosody #CoTurn #XMPP #StandardsCompliance #OwnYourData #SelfHosting

Just tested my Prosody server against the compliance checker at https://compliance.conversations.im My Prosody server got itself a 100% compliance rating, with in-band registration being disabled as it's more of a personal server than a public one, even with that public conference. If you want to see the results for yourself, check out https://compliance.conversations.im/server/simplygregario.us/ I will also point out that both Prosody and CoTurn (which provides media relay services for Prosody) are configured to be dual-stack, meaning everything works both on IPv4 and IPv6. Even got all 8 SRV records configured in DNS so CoTurn's STUN and TURN implementations will hopefully work flawlessly, both via TCP & UDP (and the TLS-based option is included). #Prosody #CoTurn #XMPP #StandardsCompliance #OwnYourData #SelfHosting

Just tested my Prosody server against the compliance checker at https://compliance.conversations.im My Prosody server got itself a 100% compliance rating, with in-band registration being disabled as it's more of a personal server than a public one, even with that public conference. If you want to see the results for yourself, check out https://compliance.conversations.im/server/simplygregario.us/ I will also point out that both Prosody and CoTurn (which provides media relay services for Prosody) are configured to be dual-stack, meaning everything works both on IPv4 and IPv6. Even got all 8 SRV records configured in DNS so CoTurn's STUN and TURN implementations will hopefully work flawlessly, both via TCP & UDP (and the TLS-based option is included). #Prosody #CoTurn #XMPP #StandardsCompliance #OwnYourData #SelfHosting

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

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

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

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.

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.

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.

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.

@mptcp

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.

@mptcp

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.

@mptcp

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.

@mptcp

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.

@mptcp

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.

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

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

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 got #matrix running on my VPS and it's working nicely, other than calling. How does #Coturn work 😭