Updated: 11 October 2026 · Applies to: WHMSonic with SHOUTcast v2 on AlmaLinux/Rocky 8 and 9
Symptom: WHMSonic shows the SHOUTcast v2 radio as online, but listeners cannot connect, and creating a radio returns an error. Cause: SHOUTcast binds to the radio's IP address, but that IP is not configured on the server's network interface.
1. Check which IPs the server has
ip -4 addr show
The server IP (or the radio's dedicated IP) must appear in the list. If it does not, add it permanently with NetworkManager (AlmaLinux/Rocky 8/9):
nmcli connection show # find the connection name, e.g. eth0 nmcli con mod eth0 +ipv4.addresses 203.0.113.25/32 nmcli con up eth0
Use the exact IP and netmask from your server details. On a Ucartz VPS, keep the VNC console open while you change network settings.
2. Open the radio ports
Allow the radio's port range in the firewall instead of turning the firewall off, for example firewall-cmd --permanent --add-port=8000-9000/tcp && firewall-cmd --reload, or add the range to TCP_IN in CSF and run csf -r.
3. Restart the radio
Restart the radio in WHMSonic and test the stream URL from outside (curl -I http://203.0.113.25:8000/).
Note: If the server only has a private IP on its interface (it is behind NAT), SHOUTcast must bind to that private IP or to all addresses; ask our support team which applies to your server.
