Where Does TeamTalk Store Server Config?
TeamTalk server reads tt5srv.xml for users and channels, with the path set by install mode on Windows and flags on Linux.
Last updated
TeamTalk keeps server state in one XML file. Users, passwords, channels, bans, and file sharing roots all live there. The client keeps a separate INI with local preferences.
Path confusion comes from install modes. The Windows service build uses ProgramData. The console build uses the user Roaming folder. Linux uses wherever the start flags say, commonly /etc/teamtalk. Check the service definition or the launch flags before editing, or you will edit a file the server never reads.
Where TeamTalk stores this, by platform
%APPDATA%\BearWare.dk\tt5srv.xml
Console server default. The NT service build uses ProgramData instead. The file holds plaintext credentials, so restrict access.
/etc/teamtalk/tt5srv.xml
Common systemd layout. Passed with the config flag at startup. Logs usually go to /var/log/teamtalk/tt5srv.log next to it.
Frequently asked questions
How do I set up TeamTalk server paths on Linux?
Run tt5srv with the wizard flag and point config and log flags at those paths. Set owner to the service user and mode 0600, since the file holds plaintext passwords.
How do I reload TeamTalk server config?
Send SIGHUP to the server process after editing. The server reloads tt5srv.xml without a full restart when the config is valid.
Where is the TeamTalk client INI file?
Check the executable folder first, then the Roaming profile. The -cfg flag overrides both, which is the clean way to run multiple clients with separate settings.
Notice an outdated path? Let us know.