Stun-Turn-Server

A basic STUN (Session Traversal Utilities for NAT) and TURN (Traversal Using Relays around NAT) server, originally created for Nextcloud Talk, that fully…

  • Communication
  • Network Services
A basic STUN (Session Traversal Utilities for NAT) and TURN (Traversal Using Relays around NAT) server, originally created for Nextcloud Talk, that fully automates the creation of the configuration files and passwords the service needs to start. It is aimed at home servers that need to relay WebRTC traffic across NAT, and removes the manual configuration a standard TURN setup would otherwise require.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

Availability: platform listings confirmed today, links checked 42 days ago

No GitHub repository data collected yet.

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Allow outbound UDP to a STUN server A STUN lookup sends a UDP packet to a server like stun.l.google.com on port 19302 to find your public IP. If your firewall blocks that outbound UDP traffic, the lookup will time out or fail. source
  • Check error messages when lookup fails If a query does not return an external address, the client can report the error and its cause. Reading that message helps tell whether DNS, network, or the STUN server is the problem. source
  • Use sensible timeout and retry settings The client can be set with a timeout and retry interval, such as 5 seconds and 500 ms, or use defaults of 10 seconds and 1 second. This matters on slow or blocked networks because it controls how long the app waits before giving up. source
  • IPv6 socket errors after startup If IPv6 is not enabled on your server, the socket errors reported right after startup are expected and can be ignored. source
  • Review settings before first start Read the descriptions of all variables and open the 'Show more settings' tab in the Unraid template before starting the container for the first time. source

Fetched 45 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Should I rely on free public STUN/TURN servers for a production Stun-Turn-Server deployment?

No, free STUN/TURN servers are only meant for development work, not for scale. You should run your own TURN server for production, and CoTurn is cited as a common implementation people use without issues.

How can I verify a newly configured STUN/TURN server is working?

The self-hosted STUN/TURN thread is specifically about how to know whether the server is working properly after installation and configuration. Use that thread to find validation methods for your deployed STUN/TURN server.

Where should I ask questions about RFC 5766 TURN and CoTurn project issues?

Use the TURN Server / CoTurn project Google Groups forum. It is described as a place to ask questions, share thoughts, and discuss TURN and STUN.

What WebRTC deployment topics are covered for STUN/TURN NAT traversal?

The guide covers NAT traversal principles, deployment, and connection setup for WebRTC network connectivity. It also provides practical examples.

Answers sourced from groups.google.com, webrtc.link, www.reddit.com, www.reddit.com

Community

Collected 53 days ago - public community threads