Skip to content

fix: remove ws disconnection errors#55

Merged
jcabrero merged 3 commits intomainfrom
fix/ws_error_msg
Jan 29, 2026
Merged

fix: remove ws disconnection errors#55
jcabrero merged 3 commits intomainfrom
fix/ws_error_msg

Conversation

@jcabrero
Copy link
Member

This PR removes the errors from the node logs as the node has a reconnection retry:

ERROR alloy_transport_ws::native: WS connection error err=IO error: peer closed connection without sending TLS close_notify: https://docs.rs/rustls/latest/rustls/manual/_03_howto/index.html#unexpected-eof
ERROR alloy_transport_ws::native: WS connection error err=IO error: peer closed connection without sending TLS close_notify: https://docs.rs/rustls/latest/rustls/manual/_03_howto/index.html#unexpected-eof

@jcabrero jcabrero changed the base branch from main to chore/add_version_number January 28, 2026 11:43
@jimouris
Copy link
Member

Is this something we have introduced or a library? It seems that it needs close_notify to properly close the socket?

@jcabrero jcabrero force-pushed the chore/add_version_number branch from 0f39176 to 3e7f73d Compare January 28, 2026 17:13
@jcabrero
Copy link
Member Author

Nope, this is just that the RPC providers sometimes introduce a maximum lifetime on connections and reset after some period. Our WS provider automatically reconnects, but these messages appear. Nothing to worry about, but better to hide the messages so users don't panic.

Base automatically changed from chore/add_version_number to main January 29, 2026 11:31
@jcabrero jcabrero merged commit 500b27c into main Jan 29, 2026
@jcabrero jcabrero deleted the fix/ws_error_msg branch January 29, 2026 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments