I was running a long-lived axum server to smoke test macOS direct connections, and I saw the following error:
ERROR ts_runtime::multiderp::uniderp: running derp client error=peer closed connection without sending TLS close_notify: https://docs.rs/rustls/latest/rustls/manual/_03_howto/index.html#unexpected-eof region_id=1
After this, my periodic curls (via a tailscaled tun device) to the axum server started failing. I only saw the error once, which suggests maybe the uniderp failed to restart itself, which would mean the incoming connection is completely dead for both data and disco (my home region is 1).
The computer running the axum server had internet connectivity both before and after the event (though a transient failure is totally possible) — after restarting the axum server the curls began working again.
I was running a long-lived axum server to smoke test macOS direct connections, and I saw the following error:
After this, my periodic curls (via a
tailscaledtun device) to the axum server started failing. I only saw the error once, which suggests maybe the uniderp failed to restart itself, which would mean the incoming connection is completely dead for both data and disco (my home region is 1).The computer running the axum server had internet connectivity both before and after the event (though a transient failure is totally possible) — after restarting the axum server the curls began working again.