Check first, change later
The generator builds matching diagnostic commands for Nginx RTMP, SRTLA receivers, OpenIRL, Restreamer, BELABOX Remote UI, and NOALBS. It only reads status information. It installs nothing, opens no ports, and restarts no services.
Look for the cause systematically
When a streaming server goes down, individual checks for CPU, memory, disks, network, open ports, services, Docker, firewall, and logs will get you there. The generator puts together a matching, read-only routine for the server profile you pick.
The output works as a starting point for your own troubleshooting or for a cleaned-up support request. Mask IP addresses, hostnames, usernames, and internal paths before you pass it on.
What each check area tells you
- System and load: show whether CPU or memory is running short.
- Disks: reveal full storage and missing free inodes.
- Network and ports: show addresses, routes, and listening TCP and UDP services.
- Services and Docker: help with stopped processes, restarts, and container errors.
- Firewall and Fail2Ban: point to blocking rules or banned connections.
Run a diagnosis in a sensible order
- Note the time of the failure and the affected stream.
- Check system load, disk space, and running services.
- Verify that the expected port is actually open and in use.
- Only then read the relevant logs.
- Back up the configuration and the current output before you change anything.
Don't restart several services at once. Make one change at a time and check whether things got better or worse. That way you can still trace the actual cause.
Choose the scope of the diagnosis
Share the output responsibly
Privacy and security
This tool works locally in your browser. IRL4YOU neither transmits nor stores what you enter. Still, keep credentials out of screenshots and public support messages.