What Is SinusBot? TS3 Music Bot Setup Guide

SinusBot is a browser-managed audio bot that lets you play music around the clock on TeamSpeak 3 and Discord servers. It is the most widely used solution for server owners who want background music in a waiting channel, a continuous radio stream, or a DJ setup for community events. This guide covers what SinusBot is, how it works, how to install and configure it, and how to fix the problems people most often run into.

What Is SinusBot?

SinusBot is software that runs on a server. It behaves like a virtual TeamSpeak (or Discord) client: it connects to your server, joins a channel and streams audio from there. Users see the bot in the channel much like a person — except it plays music instead of talking.

It provides a web panel for management. You log in from your browser, upload music, build playlists and add radio streams. You can also control it by typing commands from the TeamSpeak client.

Why do you need a separate bot?

TeamSpeak has no built-in music playback. Streaming music through your own microphone is technically possible but impractical: your computer must stay on, audio quality suffers, and the music stops when you disconnect. Because SinusBot runs server-side, it is independent of your machine and streams continuously.

What Can SinusBot Do?

• Music playback: Plays MP3, FLAC, OGG and similar files you upload to the server.
• Radio streaming: Add an internet radio stream URL for continuous live broadcast.
• Playlist management: Build lists for different moods and schedule them.
• Auto-DJ: Continues randomly or in order when a list ends, so there is never silence.
• Multiple bot instances: Run several bots from one installation, streaming different music in different channels.
• Volume control: Adjust bot volume per channel and duck it automatically while people speak.
• Permissions: Restrict who can queue tracks or move the bot, based on groups.
• Script support: Write your own plugins in JavaScript or install ready-made scripts.
• Discord support: The same installation can run as a bot on Discord servers.

What Do You Need to Install SinusBot?

Running SinusBot requires a Linux server with root access. It will not work on shared hosting, because you need to install a persistently running service and open specific ports.

Requirements

• Linux server: Debian and Ubuntu are the most common choices and have the best documentation support.
• Root access: Required to install the service and its dependencies.
• 64-bit architecture: SinusBot runs only on x64 systems.
• Sufficient RAM: A single bot instance is relatively light; running several increases requirements.
• TeamSpeak 3 client: SinusBot uses the official TS3 client for TeamSpeak mode; it is downloaded to the server during setup.
• Open ports: The web panel uses TCP port 8087 by default.

If you would rather not manage a server yourself, there are two alternatives: rent a pre-installed SinusBot package, or take a VDS and install it yourself. You can review Nubitro's ready-made SinusBot packages or set up your own on a high-performance VDS.

SinusBot Installation: The General Steps

The following outline is for a Debian/Ubuntu server. Versions change over time, so check the official documentation before installing.

1. Update the server. Refresh package lists and upgrade existing packages.
2. Install dependencies. Audio libraries and virtual display tools such as x11vnc and xvfb are required.
3. Create a dedicated user. Do not run the bot as root. Running it under an unprivileged account of its own matters for security.
4. Download and extract the SinusBot archive. Place the files in your new user's home directory.
5. Install the TeamSpeak 3 client. SinusBot needs the official client for TS3 mode; the setup script downloads and configures it.
6. Run it for the first time. On first launch it generates an admin password. Save this password — it is shown only once.
7. Register it as a service. Create a systemd unit so the bot starts automatically after a reboot.
8. Open the web panel. Browse to http://server-ip:8087 to reach the interface.

Initial configuration in the panel

1. Log in as admin and change your password immediately.
2. Create a new bot instance and set its type to TeamSpeak 3.
3. Enter your TS3 server address, port and password if applicable.
4. Set the bot's display name and default channel.
5. Start the bot and confirm it appears on your TS3 server.
6. Grant it the necessary permissions on the TS3 side — channel switching and speaking rights are the essentials.
7. Upload your music files from the panel or add a radio stream URL.

Common Problems

The bot will not connect

First verify the TS3 server address and port. If your server enforces a per-IP connection limit, the bot's connection may be refused. Some TS3 servers apply an anti-flood delay to new connections; make sure this is not blocking the bot's IP.

The bot connects but there is no sound

The most common cause is missing permissions: the bot may not have speaking rights in its channel. The second most common cause is a misconfigured virtual audio device. Check the bot logs for audio device errors.

I cannot reach the web panel

Make sure port 8087 is open in your firewall. Also check whether the service is running — if the server rebooted and no service was defined, the bot may simply be stopped.

The audio stutters

Usually caused by insufficient server resources or network jitter. Running many bot instances on the same machine can cause CPU contention. Lowering the bitrate also reduces load.

I lost my password

SinusBot allows the admin password to be reset from the command line. Connect over SSH and run the relevant command to generate a new one.

Performance and Security Tips

• Do not run the bot as root. Use a separate, unprivileged account.
• Use a strong panel password. The web panel is exposed to the internet; a weak password is effectively a route to server access.
• Put a reverse proxy and SSL in front of the panel. Fronting it with Nginx over HTTPS stops your credentials travelling unencrypted.
• Restrict the panel port. Where possible, limit access to port 8087 to your own IP.
• Keep it updated. Update both SinusBot and the TS3 client regularly; version mismatches are the single most common failure cause.
• Take backups. Back up your playlists and configuration files.
• Mind DDoS protection. Voice traffic runs over UDP, so HTTP-based protection does not filter it; protection must sit at network level. See our DDoS guide for details.

A Note on Copyright

When streaming music through SinusBot, copyright matters. There is a legal difference between personal use inside a closed community and a public, commercial broadcast. Using royalty-free music libraries, Creative Commons licensed works, or internet radio stations that have cleared their own rights is the safest route. Responsibility here rests with the server owner.

Frequently Asked Questions

Is SinusBot free?

The software itself is free up to a certain number of bot instances; running more requires a licence. The cost of the server hosting it is separate. Renting a ready-made package resolves both on the provider's side.

Can I install it on shared hosting?

No. Because SinusBot is a persistently running service that needs root access, it will not work in a shared hosting environment. A VDS or dedicated server is required.

How many bots can I run on one server?

It depends on your CPU and RAM. Each instance runs a separate TS3 client and consumes resources. When audio quality starts degrading, you are approaching the limit.

Does SinusBot work on Discord?

Yes. When creating a bot instance, select Discord as the type and enter your bot token to use it on your Discord server.

The bot stops when the server reboots — what should I do?

Register the bot as a systemd service and enable it to start on boot. Without this you will need to launch it manually after every restart.

Summary

SinusBot is the most practical way to add uninterrupted music and radio to your TeamSpeak 3 server. Installation takes some technical knowledge, but once configured correctly it needs almost no maintenance. If you would rather not manage a server, a ready-made package delivers the same result without the technical detail.

If you are unsure which setup suits you, talk to our team. You can also read our TeamSpeak 3 guide for more on choosing a voice server.