Misc options
Platform Specific Issues
Newly Added Parameters

&turn

Lets you specify a custom TURN server or disable all TURN servers.

Options

Value

Description

user;pwd;turnserveraddress

Set this TURN server to turnserveraddress with username user and password pwd

false | off

disable the use of the TURN servers

Details

Several TURN servers are provided by Steve for free, for now, and these are automatically selected based on your geographic location. You may wish to use your own privately hosted TURN server instead though, and the &turn is one flexible way to select it.

The default OBS.Ninja TURN server network address is turn:turn.obs.ninja:443

Locations

  • Montreal, Canada

  • Germany

  • Chicago

  • Los Angeles

  • France/UK

  • insecure.cam is in Hong Kong

Example Usage:

https://obs.ninja/?turn=steve;setupYourOwnPlease;turn.obs.ninja:443&privacy

More Info TURN Servers are designed to help certain users connect when they are behind a firewall or other network restriction. About 1 in 10 users need a TURN server to use OBS Ninja; if you are having problems, check to see if they are using the TURN server. Sometimes, rarely, using your own TURN server can improve video quality for some users, if the public network routing is very bad and the TURN server is hosted on a high-quality private network, like Google Cloud. Details are provided in the code repo no how to deploy your own (turnserver.md) TURN servers are NOT something you can use to share one video stream with multiple viewers. (That is an SFU server, which is out of scope of this article.) A TURN server acts like a middle-man, routing the encrypted data between two peers, mainly when those two peers are unable to speak directly themselves.

Using a TURN server can also hide your IP address from other peers. You will need to use &privacy to FORCE the TURN server to be enabled, as otherwise the system will still try to use a direct p2p connection, instead of the TURN server. You may want to add turn and privacy flags to both the viewer and the sender side, to ensure things are correctly set.

https://obs.ninja/speedtest performs a connection test using the TURN server. It will select the closest public TURN server to you. At peak hours, these TURN servers might have lower performance compared to at off-peak hours, so consider hosting your own TURN server if absolute maximum performance is needed.

You can check to see if you are using the TURN server by checking the connection stats window (Left-Click + CTRL while viewing a video. In this stats display, "Relay" implies connected to a TURN server. HOST implies connected via a LAN. SRFLX/PRFLX implies connected directly via STUN.

Installing your own TURN server

Details on how to setup and deploy your own TURN server is here, although there are also plenty of guides online for this, too.

https://github.com/steveseguin/obsninja/blob/master/turnserver.md It is possible to store credentials for your TURN server on a server, pulling them as needed via an API, such as from Twilio's API. It is also possible to hard-code the credentials into the app itself. Both these options require self-deploying the website code however.