You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Try capturing a traffic dump. Alternatively, make Websocat log traffic itself.
websocat -t - ws-c:log:tcp:node-ethereum:8545
One of reasons NodeJS-based tool can connect while other tools can't is the lack of permessage-deflate support and forced, unconditional usage of it by server.
Using strace or analogue can also be helpful.
I/O failure
What if you try to use explicit IP address instead of node-ethereum?
The problem was that websocat doesn't print that it's connected and some of the messages I was sending caused it to return I/O failure 🤦
Sorry, it was working from the beginning. It's just that a find "connected" output more convenient to know if you can start sending messages over websocket like wscat does with -c flag.
wscat -c ws://node-ethereum:8545
does connect, butwebsocat ws://node-ethereum:8545
just timeout withHow can I debug this type of error? (version
websocat 1.13.0
)The text was updated successfully, but these errors were encountered: