Connection issues
My encoder won't connect
Check your VosCast host, port, broadcast password and server type, then resolve an occupied source connection or network block.
On this page 6 sections
If your broadcasting software cannot connect to VosCast, start with the connection details in Overview → Live broadcasting in your account. Copy the fields from there rather than from an old software profile or listening link.
If the encoder stays connected but listeners hear silence or repeated buffering, use Fix buffering, dropouts and silent broadcasts instead.
Check the connection fields
Check your server software in Server settings. VosCast Server accepts either encoder mode. Icecast and SHOUTcast servers need their matching mode.
Choose the connection mode in your app, then use the table below. The host, password and port are separate fields.
| Setting | SHOUTcast | Icecast |
|---|---|---|
| Server type | SHOUTcast; use the compatible v1 mode in software whose guide specifies it | Icecast / Icecast 2 |
| Address / Host | Server address from the account, without a scheme, port or path | Server address from the account, without a scheme, port or path |
| Port | Base port shown as Standard port or Server port (SHOUTcast) | Standard port with TLS off, or TLS port (SSL) with TLS on |
| Password | Broadcast password | Broadcast password |
| Username | Usually not requested for SHOUTcast v1 | source |
| Mount point | Usually not requested for SHOUTcast v1 | Exact account mount, including its leading slash |
The broadcast password is different from your VosCast login password or server administrator password. Retype it if necessary, checking for spaces accidentally copied at either end. Do not post it in a screenshot or support forum.
For SHOUTcast, enter the displayed base port. Some encoders handle the source connection internally; do not add one to the account port yourself. For Icecast, the normal mount is often /stream, but use the exact mount shown in your account if yours differs.
Match TLS to the Icecast port
The Icecast TLS port (SSL) needs a client that supports TLS for its source connection. Turn TLS on only when using that port. Use the Standard port with TLS off when following a standard-port setup.
A TLS setting for uploading the programme is separate from HTTPS playback on your website. Changing the listening URL does not change your encoder's connection settings. Do not disable certificate checks to get past a TLS error: check the host, port, computer clock and software's TLS support first.
Another DJ or Auto DJ is already connected
Only one encoder should be supplying the station's live programme. Stop VosCast hosted Auto DJ before connecting your live encoder, and ask any other presenter to disconnect. Check for another copy of the encoder still running on this computer or another device.
Open Auto DJ in your account and use Stop Auto DJ when switching to a live source. Closing a browser tab does not stop hosted playback. After your live show, disconnect the encoder before starting Auto DJ again; this changeover is manual.
If your software keeps retrying, stop it while you correct the settings. The BUTT manual explains that BUTT continues trying to reconnect until you stop the connection.
Use a supported encoder profile
Start with MP3 at or below the account's Maximum Bitrate. Match your software's instructions to the server type rather than copying a profile for a different service.
Find the relevant walkthrough in our broadcasting software overview. BUTT and Mixxx have separate Icecast and SHOUTcast instructions. A protocol or TLS setting that is available in one application may not be offered in another.
The connection to the server is blocked by a firewall or filter
A timeout can indicate a network problem, but it does not identify the cause by itself. Check that the computer is online and that the server address and selected source port match your account.
School, workplace and guest Wi-Fi networks may restrict outgoing connections. Give the network administrator the server hostname and source port and ask whether the connection is permitted. You can compare with another network you are authorized to use. Leave security software enabled; a network block needs a suitable rule or a different permitted connection.
If the software reports a password or authentication error, review the credentials and server type first. If it reports a certificate error, review TLS. Keep the exact error text rather than treating every failure as a firewall problem.
Still unable to connect?
Contact VosCast support with:
- Encoder name, version and operating system.
- Server hostname, selected port, server type and whether TLS is enabled.
- The error text and the time it occurred, including your time zone.
- Whether hosted Auto DJ or another presenter was connected.
- Whether the same settings work from another permitted network.
Redact passwords and other credentials from screenshots and logs. Once the encoder connects, use the account's Quick Listen Link on another device to confirm that the programme is reaching listeners.