Closed srinjoychakravarty closed 1 year ago
Can you check that the hardhat.config file that is on your remote server has the correct settings? My guess is that the remote plugin (sending txs) is syncing to a different workspace/account than the local one (sending contracts data). You should be able to see in the Hardhat logs, at the beginning, which account & which workspace it's going to connect to. Make sure that:
workspace
field is set to route53-hardhatAlso, feel free to ping me on Discord if it doesn't work, I'm sure we can fix this quickly, Ethernal is supposed to work quite well with remote endpoints :)
@antoinedc pretty sure this is a bug as I have everything setup: the .env
ETHERNAL_EMAIL=*****@*****.***
ETHERNAL_PASSWORD=*********
ETHERNAL_WORKSPACE=*****
and the hardhat.config.js
module.exports = {
ethernal: {
email: ETHERNAL_EMAIL,
password: ETHERNAL_PASSWORD,
workspace: ETHERNAL_WORKSPACE,
uploadAst: true,
},
Terminal Output:
(base) ubuntu@ip-xxx-xx-xx-xx:~/xxxx$ node scripts/deploy.js
[Ethernal] Logged in with xxxxs-xxxxx@gmail.com
[Ethernal] Using workspace "route53-hardhat"
[Ethernal] Uploading contract AST, this might take a while depending on the size of your contract.
[Ethernal] Uploading dependencies ASTs, this might take a while depending on the size of your contracts.
[Ethernal] Updated artifacts for contract Bobo (0x5FbDB2315678afecb367f032d93F642f64180aa3). Dependencies: console, Strings, ECDSA, strings, Dodo, Jaaz, Crass, KeysAll, VerifiesHoly
Bobo deployed to: 0x5FbDB2315678afecb367f032d93F642f64180aa3
as I said, it works fine on localhost deployments...which is most peculiar 🤷🏽♂️
Can you check the Hardhat logs on the ec2 server? There should be some logs starting with "[Ethernal]" that print the account & workspace it's connecting to, can you post those here, please? (or send to me privately)
Can you check the Hardhat logs on the ec2 server? There should be some logs starting with "[Ethernal]" that print the account & workspace it's connecting to, can you post those here, please? (or send to me privately)
just posted it above
I meant the logs for the npx hardhat node
command
When I deploy hardhat contracts on a localhost hardhat instance using hardhat scripts, Ethernal can track Transactions just fine
When I try to use Ethernal on a remote ec2 node using a hostname over http, the hardhat/scripts deploy.js continues to deploy the contract just fine
However, Ethernal is no longer able to track any Transactions, which is very disappointing 😞