-
Notifications
You must be signed in to change notification settings - Fork 683
Ganache Stuck #4566
Comments
It sounds like you've sent a transaction with a nonce that is higher than the current nonce. |
I am also facing similar issues, especially nonce too high. In my case, I have to deploy many contracts before making the transaction to the contract. I can deploy the contracts just fine. But the problem is in some cases. For instance, I face this issue if I make a transaction to one of the contracts that calls another contract (I am using interfaces). I am sharing a little information, but if it sounds like something related, I will share more information. The entire setup is working when I do the transaction using Remix to the same local network and Metamask setup. I am not sure what's going on I am using ganache. I just tried some basic troubleshooting, like clearing the data in the advanced settings of Metamask and changing the account. But nothing helps... |
You'll need to switch to something that's maintained. Ganache is dead. If you manage to fix it in ganache and PR the change I might still be able to review, merge, and release. |
Thank you. I have been with Ganache for quite some time, and it's a great tool. I will see what is happening and post it here. Hopefully, it is helpful... If you have any suggestions on Ganache Equivalents, please advise...Once again, thank you for all the help! |
Thanks for supporting ganache over the years. Foundry's |
Thank you! |
Ganache always stuck at some time.
sometimes when you restart ganache, when want to execute transaction, it will stuck.
it trying to getReceipt
and so many net_version logs
I tried to wait a few minutes like more than 10 minutes which is already abnormal, still stuck forever i guess.
i have this logs with strict mode.
Usually by add Network again to metamask, with different port and address, it working perfectly fine again. i just wondering if this is a BUG.
would be great if ganache can reuse setting without changing port and address everytime stuck.
The text was updated successfully, but these errors were encountered: