-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The code in public_tx.js under the Deploy a smart contract operation in the Tutorials module of Private networks has significant errors, resulting in various errors when running node public_tx.js. #1546
Comments
Same happens to me, still no luck |
it was successful the first time i ran it. when I tried running it again got this error |
It´s happening the same when I try to deploy a new contract: public.js const web3Instance = new Web3('http://myserver:8541'); const privateKey = // read in the contracts // get txnCount for the nonce value const rawTxOptions = { console.log("Signing the txn") console.log("Sending transaction..."); ` InvalidResponseError: Returned error: Internal error Node.js v18.16.0 Does anyone have any ideas about this problem? |
Was anyone able to use it? |
The code in public_tx.js under the Deploy a smart contract operation in the Tutorials module of Private networks has significant errors, resulting in various errors when running node public_tx.js.
InvalidResponseError: Returned error: Transaction processing could not be completed due to an exception
at Web3RequestManager._processJsonRpcResponse (/home/haerker/besu/Permissioned-Network/node_modules/web3-core/lib/commonjs/web3_request_manager.js:258:23)
at Web3RequestManager. (/home/haerker/besu/Permissioned-Network/node_modules/web3-core/lib/commonjs/web3_request_manager.js:156:29)
at Generator.next ()
at fulfilled (/home/haerker/besu/Permissioned-Network/node_modules/web3-core/lib/commonjs/web3_request_manager.js:21:58)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
innerError: {
code: -32000,
message: 'Transaction processing could not be completed due to an exception'
},
The text was updated successfully, but these errors were encountered: