This file will contain all updates to sections.
- Per this question, if you're using WSL, for the ganache UI you'll have to use a different endpoint.
You have 4 options to fix this:
- Use the WSL endpoint on the ganache UI (this sometimes doesn't work)
- Use
ganache
from the command line - Use
ganache-cli
from the command line (not recommended) - Just use
hardhat
from the command line (you'll have to use hardhat at some point anyways!)
On the Ganache UI, you can select a different hostname and connect to whatever IP you see. In the example below, you'd connect to 172.24.224.1
You can also try to edit it by:
- Inside Ganache in the top-right corner tap on the gear icon (settings).
- Then in the server tab, change the HOSTNAME and select 0.0.0.0 - All Interfaces.
- Now replace your RPC Server URL inside the code with this latest URL that will be something like: HTTP://0.0.0.0.7545. Recheck this from Ganache.
yarn global add ganache
ganache
Keep this running in it's own terminal, and use the endpoint it gives you. To kill it, press CTRL
+ C
.
Or, optionally, you can install ganache-cli
as this user did.
yarn global add ganache-cli
ganache-cli
Keep this running in it's own terminal, and use the endpoint it gives you. To kill it, press CTRL
+ C
.
yarn add --dev hardhat
yarn hardhat
Then select the Create an empty hardhat.config.js
Then run:
yarn hardhat node
Keep this running in it's own terminal, and use the endpoint it gives you. To kill it, press CTRL
+ C
.
If your keepers are not kicking off, run through this checklist to find out why.
- Double check the subscription ID in your contract
- Double check the subscription is funded with enough LINK
- Is
checkUpkeep
returning true? - Can you call
performUpkeep
yourself? (If you can't the keeper can't!)
- Remember if you are using gitpod then you cannot connect your local hardhat node with metamask. To resolve this you can use vs code or testnets instead of local node.