octoturgeandClaude Opus 5 5a594c43a4 Include the cause chain when go2rtc cannot be reached ...

reqwest's Display is only "error sending request for url (...)" - the
reason is one or two sources down, and "connection refused" versus
"timed out" is the entire content of the message. This error is relayed
to the cloud and then to a viewer, so it is the only explanation anyone
gets for a camera that will not play.

It now reads "could not reach go2rtc at http://127.0.0.1:1984: ...",
naming go2rtc explicitly, because by far the likeliest cause is that it
is not running and an error mentioning only a port sends whoever reads
it looking at the network instead.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-10-19 00:37:27 +00:00

..

printer

Generate go2rtc's config from what the printers report

2026-10-15 23:03:02 +00:00

uplink

Include the cause chain when go2rtc cannot be reached

2026-10-19 00:37:27 +00:00

camera.rs

Answer relayed WebRTC offers from the gateway's own go2rtc

2026-10-19 00:32:57 +00:00

completion.rs

Confirm the light and the upload on a real P1P

2026-10-15 22:23:41 +00:00

config.rs

Generate go2rtc's config from what the printers report

2026-10-15 23:03:02 +00:00

fleet.rs

Add upload_project_file/send_gcode_line, real Marlin serial, Bambu protocol auto-detect

2026-09-05 20:40:21 +00:00

go2rtc.rs

Generate go2rtc's config from what the printers report

2026-10-15 23:03:02 +00:00

lib.rs

Generate go2rtc's config from what the printers report

2026-10-15 23:03:02 +00:00

main.rs

Require a password on go2rtc's API

2026-10-18 22:00:51 +00:00