Resource guide

A practical troubleshooting workflow

Copy the exact message

Record both the command and the error before changing anything. Separate shell command-not-found errors, Python syntax errors, application validation errors, connection observations, and filesystem failures.

Check the basics in order

Confirm the working directory and filename. Verify the interpreter version. Run --help. Use the literal loopback address and one known listener. Choose a fresh output filename in a writable folder. This narrows the problem without changing the whole machine.

Diagnose the fixture

If the server reports Address already in use, it did not start successfully. Pick a different unused high port and update both commands. Do not terminate an unfamiliar process just to obtain the expected screenshot.

Diagnose the output

If the tool exits with status 1, read stderr. An old report may block exclusive creation; a sidecar may already exist; a parent path may be a file. Inspect the destinations, preserve any partial artifact, and rerun with a new path.

Use tests for a narrower question

The real listener test proves a local connection can work in that environment. Mocked timeout and DNS tests prove the code handles those simulated failures. Neither substitutes for recording what happened during a real investigation.

Apply this in the complete free Project 001 lesson →

Search PythonProjects.org