Closed ETHorHIL closed 5 years ago
I'm also seeing this issue when I run parity locally with parity --config dev --unsafe-expose
. Metamask has no problem to a local instance of ganache or any of the "regular" networks like mainnet, kovan or ropsten.
https://ethereum.stackexchange.com/questions/54731/connecting-metamask-with-parity showed me the fix: parity --config dev --unsafe-expose --jsonrpc-cor=all
(not sure if --unsafe-expose
is needed for the dev
config)
@ETHorHIL sounds Metamask does not do a good job of showing the error message, thanks for the report
I am running the latest Parity release on my MBP. When I try using Metamask to switch to localhost 8545, it never ends "Connecting to unknown network".
I tried using my IPadress or localhost on the custom RPC. And I tried various (fully synched) chains like the mainnet, kovan and my local PoA network.
Using nettop shows that a connection between between Chrome and 8454 has been established...
A friend of mine has the exact same problem.