remix could not detect the metamask's account

Question

I find that unlike the other tutorial, there is no injected web3 option, but injected provider - metamask. And when I click it, the metamask shows that it is connected, however, the remix could not detect the account. I have only remix connected to my metamask. What should I do?

Answer 1

Rinkeby and Ropsten networks are deprecated since October 5th, 2022. And, no more supported by many RPC. Also, explorers are now read only. You should switch to Goerli or Sepolia.

Answer 2

Surprisingly the issue is with Rinkeby and Ropsten. If you choose ethereum main network (or any other ) on metamask, refresh the remix, and choose Injected Provider-Metamask, your main net account will be populated.

Answer 3

If you are seeing this problem on Goerli, try switching to the Mainnet, connecting to Metamask, and then switching back to Goerli. In the final step, give Remix 5-10 seconds to update the account. This worked for me as of August 2023.

Answer 4

One more way to try, which worked for me -

1. Take the backup of your code & remove all the files from your Remix workspace.
2. Completely clear the workspace & reload the remix page.
3. Create new file/s & paste the code in them.
4. Compile the code & now try to switch the Environment to Metamask.