Your device can't reach Skronk

Skronk reached your speaker or TV to start playback, but the device couldn’t connect back to stream the audio.

Playback needs both directions to work. Skronk talks to the device to control it, and the device fetches audio from Skronk over your network. The control direction worked, but the audio direction was blocked. This often means a firewall is blocking Skronk.

Skronk serves audio on a fixed port, 27429 by default, so you can allow it once and forget about it.

Open the port

First, find your network’s address range. Run:

ip -4 addr

Look at your network connection — often wlan0 or eth0 — for a line like inet 192.168.1.50/24. Your range is that address with the last number set to zero: 192.168.1.0/24. Use yours wherever you see 192.168.1.0/24 below.

Now add a rule for your firewall.

UFW

sudo ufw allow from 192.168.1.0/24 to any port 27429 proto tcp

UFW keeps this rule across reboots on its own.

firewalld

sudo firewall-cmd --permanent \
  --add-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="27429" protocol="tcp" accept'
sudo firewall-cmd --reload

The --permanent flag plus the reload make the rule survive reboots.

27429 is the default. If you changed the stream proxy port in Skronk’s settings, use that number instead.

Check that it worked

Re-attach the device in Skronk and press play. Audio should start within a few seconds.

Still won’t play?

If audio still doesn’t stream after you open the port, your device is probably on a different network than your computer. This happens when:

• Your speaker or TV is on a guest or “IoT” Wi-Fi network, separate from your computer.
• Your router has client isolation (sometimes called AP isolation) turned on, which stops devices on the network from reaching each other.

Skronk can’t cross those boundaries. Put the device and your computer on the same network, or turn off client isolation for them in your router’s settings.