TURN(1)
π GENERAL INFORMATION π
okay so bestie, turnadmin is a TURN administration tool β¨ and she's here to manage all the user accounts β adding users, removing users, and generating TURN keys for them, the whole glow-up π«Ά
but listen, for security reasons we do NOT recommend storing passwords openly π like please don't do that. the better option is to use pre-processed "keys" which are then used for authentication, and those keys? generated by turnadmin herself π
also lowkey important: turnadmin is a link to the turnserver binary, but turnadmin performs different functions. same girl, different era π
π Options note π
turnadmin has long and short option names, for most options. Some options have only long form, some options have only short form. Their syntax is somewhat different, if an argument is required:
The short form must be used as this (for example):
$ turnadmin -u <username> ...
The long form equivalent must use the = character:
$ turnadmin --user=<username> ...
If this is a flag option (no argument required) then their usage is the same, for example:
$ turnadmin -k ...
is equivalent to:
$ turnadmin --key ...
You have always to use the -r <realm> option with commands for long term credentials β because data for multiple realms can be stored in the same database. no skipping the realm bestie, she will know π«£
β¨ NAME β¨
turnadmin β a TURN relay administration tool π
π¦ SYNOPSIS π¦
$ turnadmin [command] [options]
$ turnadmin [ -h | --help]
πΈ DESCRIPTION πΈ
Commands:
-P,--generate-encrypted-passwordβ Generate and print to the standard output an encrypted form of a password (for web admin user or CLI) π The value then can be used as a safe key for the password storage on disk or in the database. Every invocation for the same password produces a different result (yes, every single time, that's the point π«). The format of the encrypted password is:$5$<...salt...>$<...sha256(salt+password)...>. Salt is 16 characters, the sha256 output is 64 characters. Character 5 is the algorithm id (sha256). Only sha256 is supported as the hash function.-k,--keyβ Generate key for a long-term credentials mechanism user π-a,--addβ Add or update a long-term user β-A,--add-adminβ Add or update an admin user π-d,--deleteβ Delete a long-term user ποΈ-D,--delete-adminβ Delete an admin user π-l,--listβ List long-term users in the database π-L,--list-adminβ List admin users in the database πβ¨-s,--set-secret=<value>β Add shared secret for TURN REST API π€«-S,--show-secretβ Show stored shared secrets for TURN REST API π-X,--delete-secret=<value>β Delete a shared secret.--delete-all_secretsβ Delete all shared secrets for REST API.-O,--add-originβ Add origin-to-realm relation π-R,--del-originβ Delete origin-to-realm relation βοΈ-I,--list-originsβ List origin-to-realm relations π-g,--set-realm-optionβ Set realm params:max-bps,total-quota,user-quotaβοΈ-G,--list-realm-optionsβ List realm params π-E,--generate-encrypted-password-aesβ Generate and print to the standard output an encrypted form of password with AES-128 π
Options with required values:
-b,--db,--userdbβ SQLite user database file name (default -/var/db/turndbor/usr/local/var/db/turndbor/var/lib/turn/turndb). See the same option in theturnserversection. ποΈ-e,--psql-userdbβ PostgreSQL user database connection string. See the--psql-userdboption in theturnserversection. π-M,--mysql-userdbβ MySQL user database connection string. See the--mysql-userdboption in theturnserversection. π¬-J,--mongo-userdbβ MongoDB user database connection string. See the--mysql-mongooption in theturnserversection. π-N,--redis-userdbβ Redis user database connection string. See the--redis-userdboption in theturnserversection. π§±-u,--userβ User name. π-r,--realmβ Realm. π-p,--passwordβ Password. π€-x,--key-pathβ Generates a 128 bit key into the given path. ποΈ-f,--file-key-pathβ Contains a 128 bit key in the given path. π-v,--verifyβ Verify a given base64 encrypted type password. β-o,--originβ Origin. π§--max-bpsβ Set value of realm'smax-bpsparameter. π--total-quotaβ Set value of realm'stotal-quotaparameter. π--user-quotaβ Set value of realm'suser-quotaparameter. π (ok it's a quota, don't come for me)-h,--helpβ Help. π
π Command examples: π
Generate an encrypted form of a password:
$ turnadmin -P -p <password>
Generate a key:
$ turnadmin -k -u <username> -r <realm> -p <password>
Add/update a user in the in the database:
$ turnadmin -a [-b <userdb-file> | -e <db-connection-string> | -M
<db-connection-string> | -N <db-connection-string> ] -u
<username> -r <realm> -p <password>
Delete a user from the database:
$ turnadmin -d [-b <userdb-file> | -e <db-connection-string> | -M
<db-connection-string> | -N <db-connection-string> ] -u
<username> -r <realm>
List all long-term users in MySQL database:
$ turnadmin -l --mysql-userdb="<db-connection-string>" -r <realm>
List all admin users in Redis database:
$ turnadmin -L --redis-userdb="<db-connection-string>"
Set secret in MySQL database:
$ turnadmin -s <secret> --mysql-userdb="<db-connection-string>"
-r <realm>
Show secret stored in PostgreSQL database:
$ turnadmin -S --psql-userdb="<db-connection-string>" -r <realm>
Set origin-to-realm relation in MySQL database:
$ turnadmin --mysql-userdb="<db-connection-string>" -r <realm> -o
<origin>
Delete origin-to-realm relation from Redis DB:
$ turnadmin --redis-userdb="<db-connection-string>" -o <origin>
List all origin-to-realm relations in Redis DB:
$ turnadmin --redis-userdb="<db-connection-string>" -I
List the origin-to-realm relations in PostgreSQL DB for a single realm:
$ turnadmin --psql-userdb="<db-connection-string>" -I -r <realm>
Create new key file for mysql password encryption:
$ turnadmin -E --key-path <key-file>
Create encrypted mysql password:
$ turnadmin -E --file-key-path <key-file> -p <secret>
Verify/decrypt encrypted password:
$ turnadmin --file-key-path <key-file> -v <encrypted>
Help:
$ turnadmin -h
π DOCS π
After installation, run the command:
$ man turnadmin
or in the project root directory:
$ man -M man turnadmin
to see the man page πβ¨
π FILES π
/etc/turnserver.conf/var/db/turndb/usr/local/var/db/turndb/var/lib/turn/turndb/usr/local/etc/turnserver.conf
π§ DIRECTORIES π§
/usr/local/share/turnserver/usr/local/share/doc/turnserver/usr/local/share/examples/turnserver
π SEE ALSO π
turnserver, turnutils π«Ά
π WEB RESOURCES π
project page:
https://github.com/coturn/coturn/
Wiki page:
https://github.com/coturn/coturn/wiki
forum:
https://groups.google.com/forum/?fromgroups=#!forum/turn-server-project-rfc5766-turn-server/
π AUTHORS π
See the AUTHORS.md file in the coturn source distribution.
and that's the whole vibe bestie π«Ά this was TURN(1), and she's dated 17 May 2026 β so if you're reading this, hi from that exact day, ily, go generate some keys πβ¨π
π¦ where this page comes from
- arch rolling: coturn 4.18.0-2 Β· LicenseRef-coturn
- epel 10: coturn 4.18.0-1.el10_3 Β· BSD-3-Clause AND MIT
- epel 9: coturn 4.18.0-1.el9 Β· BSD-3-Clause AND MIT
- fedora 43: coturn 4.18.0-1.fc43 Β· BSD-3-Clause AND MIT
- fedora 44: coturn 4.18.0-1.fc44 Β· BSD-3-Clause AND MIT
- nixos 26.05: coturn 4.16.0
- nixpkgs unstable: coturn 4.17.2
- opensuse-leap 16.0: coturn 4.14.0-bp160.1.1 Β· BSD-3-Clause
- opensuse-leap 16.0: coturn 4.14.0-bp160.1.1 Β· BSD-3-Clause
- opensuse-leap 16.0: coturn 4.14.0-bp160.1.1 Β· BSD-3-Clause
- opensuse-leap 16.0: coturn 4.14.0-bp160.1.1 Β· BSD-3-Clause
- ubuntu stonking: coturn 4.18.0-1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms