I installed dietpi dashboard on my raspberry pi-B2 & intel nuc both devices yesterday night. after running some time correctly on both devices. this app itself killed & the log file show this type of error
Nov 13 18:14:43 DietPi dietpi-dashboard[409]: thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Protocol("Connection reset without closing handshake")', src/sockets.rs:295:58
Nov 13 18:14:43 DietPi dietpi-dashboard[409]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Nov 13 18:14:43 DietPi systemd[1]: dietpi-dashboard.service: Main process exited, code=killed, status=6/ABRT
Nov 13 18:14:43 DietPi systemd[1]: dietpi-dashboard.service: Failed with result 'signal'.
Nov 13 18:14:43 DietPi systemd[1]: dietpi-dashboard.service: Consumed 4.519s CPU time.
after restart dietpi-dashboard it is again start & start running. so i do not have any idea why this app killed by both dietpi systems.
& in another device the error log is like this
Nov 13 17:34:12 DietPi dietpi-dashboard[41875]: thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })', src/sockets.rs:295:58
Nov 13 17:34:12 DietPi dietpi-dashboard[41875]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Nov 13 17:34:12 DietPi systemd[1]: dietpi-dashboard.service: Main process exited, code=killed, status=6/ABRT
Nov 13 17:34:12 DietPi systemd[1]: dietpi-dashboard.service: Failed with result 'signal'.
Nov 13 17:34:12 DietPi systemd[1]: dietpi-dashboard.service: Consumed 13.059s CPU time.