Timeout error when I tried to send transaction
See original GitHub issueI don’t understanda why, but since few days, I can’t send transaction.
When I do web3.eth.sendTransaction(transaction)
I’ve this error timeout: timed out
.
the transaction looks like this : transaction = {'from': user2, 'to':user1, 'data': web3.toHex("test")}
And user1
and user2
are defined . Accounts are unlocked and have gas…
Have you got any idea?
Issue Analytics
- State:
- Created 7 years ago
- Comments:19 (6 by maintainers)
Top Results From Across the Web
Send transaction crash, how to resolve "timeout" error?
1 Answer 1 · Check that the node is running, restart the node · Monitor your system load (available memory, CPU, use top...
Read more >How to resolve timeout error while executing transactions in ...
I'm trying to insert bulk data in to blockchain. For 11,000 records records the insert is happening without any fault. But if I...
Read more >Read and Connection Timeout Handling | Paylosophy
Read timeout occurs when the socket is open, connection to the host server is established, the request is sent, but the response from...
Read more >Transaction Submission, Timeouts, and Dynamic Fees FAQ
Getting more errors than you anticipated when submitting transactions to Stellar? Unsure how to deal with them? This FAQ is for you!
Read more >Troubleshoot common connection issues to Azure SQL ...
These connection problems can be caused by reconfiguration, firewall settings, a connection timeout, incorrect login information, or failure to ...
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 FreeTop 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
Top GitHub Comments
For future readers who encounter this problem, one way to resolve it is by changing this:
To this:
As the default timeout is 10 (seconds).
@shanefontaine: It involves inter-process communication, so technically speaking, any time-duration is possible, especially when the communication is over HTTP. Evidently, they added the
timeout
configuration parameter, so there’s gotta be good reason for that, wouldn’t you agree? Practically, the reason I wrote this is because I ran into a sporadic timeout scenario, which I was able to resolve by increasing the timeout. By the way, it’s not about sending a transaction, it’s about receiving a response to it (on the client side, where you configure the timeout).