I was trying to follow a tutorial from devto.io and to send transactions to the smart contract, I would need to connect my MetaMask wallet using one of the accounts created when I ran npx hardhat node command.
To do so, I opened MetaMask and updated the network to be Localhost 8545, but Metamask didn't connect to it and showed errors like the following screenshot.
I think that you probably interrupted the node you launched when you typped :
npx hardhat node
You should keep it running, open another terminal for the rest of the tutorial.
Also you could check the output of this command. Is it indicating something else than ? :
Started HTTP and WebSocket JSON-RPC server at http://127.0.0.1:8545/
You most likely entered wrong URL into RPC-URL input: "http://localhost:8545". SInce in config file, hardhat has chainId:1337, it may be using ganache under the hood.
If you entered correct config but it still does not connect, you could use ganache-cli. http://localhost:8545 is for ganache-cli. You should be installing ganache-cli globally and then start the server on terminal if your hardhat node has an issue
ganache-cli
When you run the command on the terminal, you will get the local public and private keys:
After setting the network you could import an account in one of those private keys:
if you click on the logo next to the network name, you will see the option import account. note that everytime you run a new command ganache-cli it will generate new private keys, so you have import a new account.
ganache gui listens to "7545" but ganache-cli listens to "8545"
What worked for me, in this case, is This video
I downloaded Ganache from the following link
Installed it and just hit the Quick Start
It will launch the ganache as shared below in the screenshot. You can see the Network ID and RPC Server details.
As a Next step, delete the HTTP://localhost:8545 network and create a new network with Ganache RPC Server details and Network ID as shared below. I have just changed my port from default to 3000.
Here you Go!
Hope it helps. Also, feel free to share your thoughts if you have other approaches as I am also in the learning phase :-)
Thanks.
What helped me was following these steps :
Step 1: Install Ganache and then launch the application.
Step 2: Check the RPC SERVER on the navigation bar and note it down.
Step 3: Open Metamask network settings. Delete the original localhost network.
Step 4: Add a new Ganache localhost network with the following configuration:
Network name - Whatever you want (Example: Ganache localhost)
New RPC URL - RPC server noted from Ganache.
Chain ID - 1337
Currency Symbol - ETH
Press Add network
You probably have a IPv6 address that is not listening on that port.
e.g.
$ ping localhost
PING localhost.localdomain (::1)...
either remove that line from /etc/hosts (e.g. ::1 localhost.localdomain localhost) or point ethermask to 127.0.0.1 instead of localhost
The error is most simple that you probably think, the default chain id for test networks in metamask is not the same as the hardhat chain id, you should go to metamask, then config, networks, localhost and change chain id to 31337
Related
I finally decided to run a chainlink node on kovan, so I followed this link https://www.youtube.com/watch?v=t9Uknfw27IU&list=LL&index=8&t=555s on how to set up the node and after a few hours of work I made it happen. So after SSH tunneling into localhost:6688 I got the GUI for the chainlink operator and wrote in the password and got in.
So the next day I decided to program some jobs on the node and did the same thing as last day and got the
site can`t be reached - ERR_CONNECTION_RESET when SSH tunneling in localhost:6688 and I can see that the CL node is running in the linux box with no errors and note I dont own a router.
What I tried so far:
-switching browsers
-temporarily disabled the windows firewall
-manually opening up the port 6688
-deleting the VM instance on Google cloud platform and creating a new one
-double checking the .env file if database and other info from GCP and infuras
WSS were correct
-check the proxy settings
-cleared browser history and cookies
-deleted Winsock catalog entries
None of this has helped to resolve this issue, any help or suggestions would really be appreciated...
Managed to fix the issue myself, If anyone has the same error try this: go to your GCP and go to VM istances - firewall and add an exception for port 6688, then copy the externalIP , add it as your localhost= externalIP :6688...worked for me.
I am new to Cosmos SDK and I just forked the official Cosmos SDK nameservice tutorial. It works well on my local machine so I just deployed it to cloud server and I want to access it thru nscli from my local machine.
First I configured nscli to set the node to remote server address on my local machine
nscli config node tcp://{{my remote server ip here}}:26657
Then I tried to run the following query
nscli query account $(nscli keys show jack -a)
Finally I got some error like ERROR: ABCIQuery: Post failed: Post "{{my remote server ip}}:26657": dial tcp : connect: connection refused
I am curios since I don't think there is any network related problem in my case. Did I mis-configured something?
Thank you very much!
Best,
Min
My config file is configured to listen on 127.0.0.1:26657, which should be set to 0.0.0.0:26657 instead. So the connection succeeded if I start the daemon node like tendermint node --rpc.laddr=tcp://0.0.0.0:26657
I am running this example http://kaaproject.github.io/kaa/docs/v0.10.0/Programming-guide/Your-first-Kaa-application/ .
But data is not storing on the server side.
What should I do now?
When I running db.logs_my_application_token.
find() from mongo console,
it is showing nothing.
Do I have to provide some IP or host in my code, I am using KAA SANDBOX from AWS.
Console Output of Raspberry Pi attachedenter image description here here...
Finally I am able to do that using ..
Perform these two steps may be this can solve your problem.
Just run this command on host machine
sudo /usr/lib/kaa-sandbox/bin/change_kaa_host.sh $new host name/ip$
Then change the IP address of using Admin UI, for that you need to
sign in using username : kaa and passwword : kaa123
then go to setting > general setting then change the IP address preceded by :8080, enter your machine's public IP address, that can be easily accessible from anywhere.
Tips :: if you are using AWS instance then use public IP address of your instance.
Further error persist then drop your previous instance and launch a new instance.
For more details go the official documentation page
Hope it will be helpful for you.
You do not need to provide IP address.
You should download the generated SDK file and compile it with the source code. and then run it.
This might seem like a duplicate question but it is not. I tried to go through similar questions but I couldn't find a fix for my problem. Here is my problem:
I need to set up an ftp connection on company servers.
I can easily connect to ftp server from fileZilla on my PC but when I try it over one of the server machines to the file server all I see is the following:
Response: fzSftp started
Command: open "*****#***.***.***.**" **
Error: Connection timed out
Error: Could not connect to server
Status: Waiting to retry...
Status: Connecting to ***.***.***.**...
Response: fzSftp started
Command: open "*****#***.***.***.**" **
Error: Connection timed out
Error: Could not connect to server
I googled the "Connection timed out"
error and I realized that the first place to check is firewall or router setting. these are outsourced to another company and they say that the issue is solved and it should work fine. I don't know where to look at.
I've had lots of issues with Filezilla. You may try another software first to see if Filezilla itself is the issue.
If you're on Windows, I highly suggest the open source project WinSCP (https://winscp.net/eng/download.php). For Mac, Cyberduck (https://cyberduck.io/?l=en) is solid (and free), though you may prefer Transmit.
I was having this problem after upgrading Filezilla. I downgraded it to a previous version and it worked like charm. I came across this ticket thread and it was absolutely helpful : Filezilla Support Ticket
Check your security group rules. You need a security group rule that allows inbound traffic from your public IP address(Google: What is my ip?) on the proper port.
Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
In the navigation pane, choose Instances, and then select your instance.
In the Description tab, next to Security groups, choose view rules to display the list of rules that are in effect.
For Linux instances: Verify that there is a rule that allows traffic from your computer(public ip) to port 22 (SSH).
For Windows instances: Verify that there is a rule that allows traffic from your computer(public ip) to port 3389 (RDP).
Also take a look at here and here for more details
I need to set up an ftp connection on company servers. I can easily connect to ftp server from fileZilla on my PC but when I try it over one of the server machines to the file server all I see is the following:
<failure to connect code>
Please note that public IP and internel IPs will be a different address; such as 123.456.675.574 for the public but internal to the server network it will be something more like 192.168.10.574 .
This is why you can easily connect from your PC because it uses the public IP address but from the internal IP network of the company servers that address will not be valid, and the internal one would need to be used instead.
Try this, 200 is just an example, just increase it and try.
Edit --> Settings --> Connection --> Timeout in seconds = 200
I'm using STS (SpringSource Tool Suite) which comes with VMware vFabric tc Server Developer Edition v2.6. The problem is, every time I start it, it shows the following error:
Port 8080 required by VMware vFabric tc Server Developer Edition v2.6
is already in use. The server may already be running in another
process, or a system process may be using the port. To start this
server you will need to stop the other process or change the port
number(s).
I don't have anything using that port that I know of. It has always worked fine until today.
I've also tried to change the port number but it doesn't accept the changes. If I change it to 8081, for example, and then restart STS it overwrites the port and sets it back to 8080.
Can anyone offer some ideas to fix this?
FYI I'm running STS in VirtualBox.
Thanks!
This applies to the latest STS version - 3.0.0
When you open STS, in the Package Explorer view (on the left), you should see a project folder called Servers.
Open Servers > VMware vFabric tc Server Developer Edition v2.7-config > catalina.properties
At the bottom of the file, you will see 2 properties defined:
bio.http.port
bio.https.port
Change bio.http.port to some other port than 8080 (e.g. 8081)
Change bio.https.port to some other port than 8443 (e.g. 8444)
Click 'Save'.
Now, when you do your right-click deploys to the built-in tc Server and start it up, it should run on the new port(s). Good luck!
In the Servers view, double click the server you wish to change the ports on. This brings up the Overview page.
Expand the Ports tab and enter your desired port settings.
The reason STS uses this configuration page is it allows you to configure a workspace server without altering the configuration in your server installation directory.
Or you might want to directly kill the zombie process still bound to that port with an oneliner:
sudo kill -9 `lsof -ti:8080`
In conjunction with Gareth's suggestion, this is what workerd for me:
In the Servers view, right click your server and click Monitoring -> Properties
Stop the monitor listening on port 8080.
Save changes and start the server.