Check and troubleshoot
Find problems in files and setups before they reach production.
A configuration that starts is not the same as one that is safe: a port open on every interface, a password inside the file or a container with more privileges than it needs all run without an error. The tools here look for those problems and explain how to fix each one.
Checks run in your browser, on what you paste. Nothing is uploaded or stored, and a static check is not a security audit: it finds known patterns and says what it cannot see.
A path through this category
- Check what you have
Paste the file you run today and read every finding with its fix.
- Fix and check again
Apply the fixes that fit your setup and run the check again until nothing serious is left.
- Regenerate when it's simpler
If the file needs more work than it is worth, generate a new one from a template and compare.
Tools in this category
- Docker Compose AnalyzerStatic checks for a docker-compose.yml, in your browser. Nothing leaves this page.Open the tool
- cloud-init validatorPaste the user-data you are about to give a new server and get findings that say what to change and why, each tied to the cloud-init documentation. The file stays in this browser; a private key in it is masked at once.Open the tool
- Docker Compose diffPaste two versions of a Compose file and see what really changed, and which changes make it riskier. Key order and short or long syntax do not count. Both files stay in this browser.Open the tool
- Dockerfile linterPaste a Dockerfile and get findings that say what to change and why, each tied to Docker's own documentation. The file stays in this browser, and secrets in it are masked.Open the tool
- DNS go-live checkerBefore you point visitors at a new server, check what DNS really answers: whether the name resolves to your server's address, whether the resolvers already agree, and whether anything will stop the certificate. Your browser asks two public resolvers directly; nothing goes through or stays with ANAROQ.Open the tool
- Docker subnet conflict checkerEnter your LAN and VPN ranges, or paste ip route output, and see which Docker networks would collide with them, and a pool that avoids them for daemon.json. Nothing you enter or paste leaves this page.Open the tool
- Production readiness checklistBefore a self-hosted server goes live, go through what usually breaks first. Each item says what to check, gives a read-only command to run on the server, explains why it matters and links to the tool on this site that helps. Your marks are kept in the link, never sent.Open the tool
Background: Troubleshooting self-hosted servers