i have deployed an private ethereum network.in metamask while adding new its working for on Localhost:8545 or http:127.0.0.1:8545 .but when i add it with 192.168.0.5{my local address} it show error "Could not fetch chain ID. Is your RPC URL correct?".
i have tried it with mac and ubuntu on same machine and network.
Related
I have created a private Cloud SQL instance in an app project. The network used is a shared VPC and it is hosted in a network project.
In the shared VPC:
The private access connection is enabled
An automatic internal IP range has been allocated for private connection
A private connection has been created
If I go to the VPC Network > VPC Network Peering page, I don't see a peering connection named cloudsql-mysql-googleapis-com. Therefore, I cannot connect to my cloud SQL instance using its private IP address. I can only reach the cloud SQL instance using its public IP address.
The same infrastructure works for the development environment, I use terraform to generate the GCP resources. The two environments have exactly the same configuration.
Source code: https://gitlab.com/Chabane87/cloudsql-issue
Does anyone know when this problem can happen?
Thanks
Based on the discussion about this issue on our another support channel, it seems connectivity tests were run to zero in on the problem. While the connection from one of your instances to Cloud SQL succeeded using public IP, it failed when using private IP but that is the intended behaviour.
The Telnet test was conducted later using live traffic from the instance to Cloud SQL and found that a port is missing in the production environment while it is defined correctly in the development environment and hence it is confirmed there is no issue with the Networking. So, please try to connect to the Cloud SQL after adding the missing port to the prod project.
I made an app that interacts with a smart contract in the local ganache-cli server, with everything working fine, after restarting the server (and deploying againg the contracts) the app seems to not find the contracts. This is the error that I receive:
Error: UserController has not been deployed to detected network (network/artifact mismatch)
I've deployed the contracts and restarted the server multiple times but nothing seems to works, also MetaStack is able to interact with the server.
Try using the --reset --all flags which tends to resolve this issue.
Steps to reproduce:
Start local geth node with following command: geth --rinkeby
--rpc --rpcaddr "127.0.0.1"
Connect metamask chrome extension to http://localhost:8545
Create a new ethereum account, ABC, on metamask
New account is visible on https://rinkeby.etherscan.io
Transfer some ethereum to ABC on rinkeby network
On Metamask, we can see ABC balance is increased on rinkeby network
However, we see ABC balance as zero, no change on localhost:8545
We checked the block number on local instance of geth, it is greater than the transaction block, so this means new block is downloaded to local instance of geth.
We couldnot figure out why Metamask is still showing the balance 0 when it is connected to localhost:8545. Your helps are appreciated.
Etherscan image
Block image
Metamask image
Metamask error image
I am currently setting up my first GCE kubernetes cluster, having previously used mainly AWS for this.
Cluster is up and running and can access a local NFS server on the same compute engine VPC via private IP, so one stage of private network connection is fine.
Cloudsql server is running and can access this fine from the cluster if I open up public ip to the world.
Have enabled private ip address on the cloudsql which looks good, but I cannot ping or connect from the same container that can reach the public ip.
Cloudsql private ip is a different subnet which I believe is to be expected.
Checked VPC Network peering and got a relevant looking rule.
Checked VPC routes and got the matching peering route with next hop.
I have seen in docs that private ip is still beta, so guess potential to be a glitch beyond my control.
Also read up on running a proxy container inside each pod - hesitant to do this unless only option, app may end up across platforms so would prefer more standard config.
There's currently a requirement that the GKE cluster must be created with "VPC-Native" networking in order to access Cloud SQL via private IP. Unfortunately you need to re-create the cluster in order to make it VPC-Native.
https://cloud.google.com/kubernetes-engine/docs/how-to/alias-ips
I have successfully deployed a solidity contract locally with Ganache.
I would now like to interact with it via http://remix.ethereum.org/
In the remix editor,I have selected the "web3 provider" and connected to my local Ganache at "http://127.0.0.1:7545"
I have inserted my contract's Address in the "At address" section, but I continually connect to the default "Ballot" contract provided by remix.
Can anyone help me connect to my locally deployed contract?