“Uncaught Error: invalid address” AND “Internal JSON-RPC error” while working with MetaMask and quorum-maker #5712
Labels
area-documentation
Issues relating to documentation, in the codebase and off.
I'm trying to get a Website running, which has a script on one page, that is calling a setParameter function from a Smart Contract and a script on another page is calling a getParameter function from the same smart contract. All that works perfectly fine in remix (with injected web3 I get the MetaMask popup with the transaction 10/10 and the contract works like a charm) . But running it on the website, I get the error:
in 9/10 times. In 1/10 times, the MetaMask UI opens and I can confirm the transaction.
Then, on the next page (where the getParameter is happening) I get:
MetaMask - RPC Error: Internal JSON-RPC error. {code: -32603, message: "Internal JSON-RPC error."}
thats happening on the first time the page loads, after that I just don't get the Value of the parameter displayed and there is just an empty box without any errors...and sometimes (when spamming F5) I get the the Value to be dispalyed! All of this seems to appear pretty random..
Script Code Page 1:
Script Code of Page 2:
To Reproduce
I'm running 3 Nodes, each on its own EC2 instance, made with the quorum-maker tool. Than I have a Webserver (EC2 aswell) which hosts the website. I also tried to host the website local on my PC with "web server for chrome", I get the same issue.
So you need different EC2 instances where you run the above mentioned tool. Then you run a simple html file where you paste the script and a
<div>
and so on to display the value.You download the "Web Server for Chrome" Plugin and host these files as a "website".
Expected behavior
I expect to get on the website, the script gets executed, the parameter is getting set, I click on a button and get on the other page, where the value of the parameter is displayed. In a very rare case, when both functions work on the first try, thats exactly whats happening.
Details:
What I tried:
-changed the Node, which the GUI is connected to
The text was updated successfully, but these errors were encountered: