L1 connection error

2025-05-02T07:25:56.007143Z  INFO taiko_preconf_avs_node::node: | Epoch: 83     | Slot: 11 | L2 Slot: 1  | Pending txs: 0    | b. fee: 10000000 | Batches: 0 | Preconf, Submit |
2025-05-02T07:25:57.526279Z ERROR alloy_transport_ws::native: WS connection error [3merr=WebSocket protocol error: Connection reset without closing handshake
2025-05-02T07:25:57.526359Z  INFO alloy_pubsub::service: Reconnecting pubsub service backend.
2025-05-02T07:25:57.526464Z ERROR alloy_pubsub::service: pubsub service reconnection error [3merr=IO error: Connection refused (os error 111)
2025-05-02T07:25:58.005002Z  WARN taiko_preconf_avs_node::node::operator: Warning: failed to check next epoch operator: Failed to get operator for next epoch: backend connection task has stopped
2025-05-02T07:25:58.005035Z ERROR taiko_preconf_avs_node::node: Failed to execute main block preconfirmation step: Failed to get operator for current epoch: backend connection task has stopped
2025-05-02T07:26:00.004863Z  WARN taiko_preconf_avs_node::node::operator: Warning: failed to check next epoch operator: Failed to get operator for next epoch: backend connection task has stopped
2025-05-02T07:26:00.004908Z ERROR taiko_preconf_avs_node::node: Failed to execute main block preconfirmation step: Failed to get operator for current epoch: backend connection task has stopped

Start by tracing the taiko_preconf_avs_node::node and taiko_preconf_avs_node::node::operator paths around the logged failure, then inspect the alloy_transport_ws and alloy_pubsub reconnection errors. Reproduce or diagnose the L1 connection reset and refusal, and confirm that operator checks and main block preconfirmation recover without the backend connection task stopping.