← Zurück zum Help-Center
Troubleshooting 5 min read

Fixing Connection Problems

Not receiving an SRT stream? Checklist for firewall, port 9999, bitrate, and latency.

Fixing Connection Problems

"My encoder says 'connected', but FizzyPeak shows Offline." That's the most common IRL streamer nightmare. Work through this checklist strictly from top to bottom — in 95% of cases the issue is one of these points.

1. Check the stream ID format

The SRT URL must contain streamid=publish:YOUR-KEY, not just the key.

Wrong:

srt://ingest.fizzypeak.stream:9999?streamid=YOUR-KEY

Right:

srt://ingest.fizzypeak.stream:9999?streamid=publish:YOUR-KEY&latency=2000

Without publish:, the server doesn't recognize you as an authorized encoder.

2. Check the stream key

  • Did you copy the current key from the setup guide? Keys get rotated if you've clicked around.
  • No leading/trailing space (a common copy-paste error)
  • No \n or line break in the key

3. Port 9999 / UDP

SRT runs over UDP port 9999 (not TCP). Firewalls that only open TCP block SRT silently.

At home (router)

Normally outbound is open. In case of carrier-grade NAT or an enterprise firewall:

  • Port 9999/UDP outbound must be open
  • No inbound rule needed (client -> server only)

LTE/5G networks

Some German mobile carriers (e.g. Vodafone Prepaid, 1&1 network mix) block UDP > 1024 on plans under €5/month.

Test: nc -u ingest.fizzypeak.stream 9999 from the same network -> should not give "Host unreachable".

4. RTMP alternative

If SRT just won't work: try RTMP (port 1935/TCP). It's slower, but extremely resistant to firewalls.

rtmp://ingest.fizzypeak.stream/live
Stream-Key: YOUR-KEY

Details: OBS Setup.

5. Bitrate too high for the network

Your Belabox sends 6000 kbps, but your LTE modem only manages 3000 kbps? -> The encoder drops packets, FizzyPeak doesn't get a complete GOP and shows "Offline".

  • Speedtest on the same network: speedtest-cli or fast.com
  • Bitrate: at least 30% below your measured upload

6. Latency too low

Mobile networks can have jitter spikes of 500-2000ms. If your SRT latency is lower than the jitter, the stream falls apart.

  • 2000ms — city, good LTE
  • 4000ms — travel, unstable network
  • 8000ms — abroad, roaming

In the URL: ?latency=4000

7. Already an active stream

FizzyPeak allows one ingest per account. If you push from two devices, only the first one gets through.

Check: Dashboard -> Go Live -> Status. If it says "Online" even though your current encoder isn't pushing yet, an old stream is still active.

Fix: wait 30 seconds (idle timeout) or rotate the key.

8. VPN conflicts

An active VPN can send SRT packets on a different route than the control messages -> the server sees packets that don't belong together and drops the stream.

  • Keep your VPN off during IRL streaming
  • If needed: a VPN with UDP support (WireGuard/OpenVPN-UDP) instead of a TCP tunnel

9. Read the encoder logs

Belabox

SSH into the Belabox: journalctl -u srtla -f. Look for:

  • CONN_ERROR -> network problem
  • REJECTED -> stream ID/key problem
  • TIMEOUT -> latency too low

OBS

Help -> Log Files -> View Current Log. Look for "Connection".

Moblin

Settings -> Debug -> Show Log. Look for "SRT" or "socket".

10. Check FizzyPeak status

Global outages are rare, but possible. Check status.fizzypeak.stream or the #status channel in Discord.

Debug command

If you want to help a support agent gather data:

# From the same device/network
ping -c 10 ingest.fizzypeak.stream
nc -zvu ingest.fizzypeak.stream 9999
dig ingest.fizzypeak.stream

The outputs immediately tell us whether it's a network or config problem.

If nothing helps: Discord #support channel with (1) your encoder type, (2) encoder log lines from "connect" onward, (3) the output of the debug commands above. We usually reply within 1h.

Noch Fragen? Öffne das Dashboard oder schreib im Discord #support.