Error: 13 INTERNAL: Received RST_STREAM with code 0
See original GitHub issueDescription
This error occurred randomly when making a transfer transaction or token association. I tried to wrap the transaction in a retry loop with a delay of 6000 ms but still having the same result. Should I override the behavior with .setNodeAccountIds() on retry when this error occurred ?
Steps to reproduce
/* Retry the Associate Function 4 times with 6000 ms of delay between each */
this.retryOperation(this.associate(accountId, tokenId, client, privateKey), 6000, 4)
/* Function to Associate a Token */
async associate(accountId, tokenId, client, privateKey) {
// Associate a token to an account
const tx = new TokenAssociateTransaction()
.setAccountId(accountId)
.setTokenIds([tokenId])
.freezeWith(client);
// Sign with the private key of the account that is being associated to a token
const signTx = await tx.sign(await PrivateKey.fromString(privateKey));
// Submit the transaction to a Hedera network
const txResponse = await signTx.execute(client);
// Request the receipt of the transaction
const receipt = await txResponse.getReceipt(client);
// Get the transaction consensus status
const transactionStatus = receipt.status;
}
Additional context
No response
Hedera network
mainnet
Version
v2.0.30
Operating system
Linux
Issue Analytics
- State:
- Created 2 years ago
- Comments:26 (1 by maintainers)
Top Results From Across the Web
[grpc-js] Error: 13 INTERNAL: Received RST_STREAM with ...
The code 0 indicates that the server did consider the stream to be complete. I have a guess about what that means, and...
Read more >JS SDK v2.0.16 Error: 13 INTERNAL: received RST_STREAM ...
At the moment, there are three endpoints which aren't working very well and result in an RST_STREAM error which the SDK doesn't handle...
Read more >grpc/grpc - Gitter
But when i deployed server app on remote server i started recieving this error: StatusCode="Internal", Detail="Received RST_STREAM with error code 0".
Read more >13 INTERNAL: received RST_STREAM with code 0-node.js
At the moment, there are three endpoints which aren't working very well and result in an RST_STREAM error which the SDK doesn't handle...
Read more >GRPC Core: Negative HTTP/2 Interop Test Case Descriptions
Server sends a RST_STREAM with error code 0 after sending all of the data to the client. Certain client languages allow the data...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@derdis14 @scalemaildev @tim-dewit I believe the reason you hit those errors was because the network was down during the weekend.
@topshef Have you tried using version 2.3.0 or 2.4.1? I believe this is when this issue was resolved. For any version before those you’d need to remove the nodes from the network manually.
Unfortunately, I this is not possible right now. However, we are currently working on implementing support for multiple IPs per node account ID which would then allow us to use the full network from Hedera instead of just one IP per node account ID. This would then allow us to at the very least hard code the entire network from status.hedera.com