Local check, no file upload
Everything is processed in your browser only. Still, remove real tokens, passwords and stream keys before you share a config with anyone else.
Catch common config mistakes early
The checker looks at NOALBS JSON, Docker Compose files and Nginx RTMP configs using rules you can follow. Among other things, it flags missing required values, unsafe example entries and odd structures before the file goes on a server.
The result complements the official documentation for each tool, but it does not replace a real syntax, container or security test. After every change, check the config with the tool it is meant for, and test outside your important live stream first.
Which files can you check?
For NOALBS, the tool checks the JSON structure and suspicious example values. In Docker Compose files, it looks at services, images, ports and typical placeholders. For Nginx and Nginx RTMP, it examines recognizable blocks, directives and risky open access.
The formats follow different rules. So pick the right file type before you paste; otherwise the hints can be incomplete or misleading.
How to read error, warning and note
- Error: The structure or a required value looks incomplete and should be fixed before you use the file.
- Warning: The config may work, but it contains a risky or commonly problematic setting.
- Note: A point can't be decided reliably locally and has to be checked in the target system.
After the local check, always use the original program: have it parse the JSON, run docker compose config, or test Nginx with nginx -t. Only then reload the service in a controlled way.
Check a config
A deliberately limited check
The tool uses plain rules for typical mistakes. It doesn't start a container, doesn't load an Nginx config and doesn't run a full security test of your server.
Privacy and security
This tool runs locally in your browser. IRL4YOU neither transmits nor stores what you enter. Credentials still don't belong in screenshots or public support messages.