-
Notifications
You must be signed in to change notification settings - Fork 514
Closed
Labels
s-noopCannot be worked onCannot be worked on
Description
What is the bug?
Nodejs app fails to submit message using the public nemes.farcaster.xyz:2283 URL using HubRpcClient from @farcaster/hub-nodejs.
The error messages I'm getting:
- for
makeUserDataAdd:Error submitting message to hub: HubError: read ECONNRESET - for
makeCastAdd:Error submitting message to hub: HubError: Call cancelled
How can it be reproduced? (optional)
This bug relates to the write data example in the hub-nodejs package. In my clone I am using the getInsecureHubRpcClient method to create the client using the public hub URL nemes.farcaster.xyz:2283.
Additional context (optional)
Add any other context about the problem here.
- I've checked that the public key of the signer corresponds to the one recorded onchain by the
KeyRegistrycontract. - My feeling is that it's a problem with using the
getInsecureHubRpcClientinstead ofgetSSLHubRpcClientbut I'm not sure if there is a username and password available to use with the public server. - It seems I'm only getting this error for submitting messages. e.g. I can run the
chron-feedexample without any problem.
Metadata
Metadata
Assignees
Labels
s-noopCannot be worked onCannot be worked on