search

MetaMask / metamask-extension

:globe_with_meridians: :electric_plug: The MetaMask browser extension enables browsing Ethereum blockchain enabled websites
https://metamask.io
Other
11.71k stars 4.79k forks source link

[Sentry] [Bug]: Metamask fails to load if no response from RPC #15629

Open JABirchall opened 1 year ago

JABirchall commented 1 year ago

Describe the bug

Metamask extention doesnt load, console errors log no response from RPC.

Steps to reproduce

I dunno

Error messages or log output

Setting up Sentry Remote Error Reporting for 'production': SENTRY_DSN sentry-install.js:1:1041
Removing intrinsics.Object.hasOwn sentry-install.js:1:102934
Content Security Policy: The page's settings blocked the loading of a resource at eval ("script-src"). moz-extension:9430:29
Content Security Policy: The page's settings blocked the loading of a resource at eval ("script-src"). moz-extension:4421:4
undefined sentry-install.js:1:102934
    h moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/sentry-install.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    default moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-6.js:1
    send moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    a moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/sentry-install.js:1
    (Async: setTimeout handler)
    a moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/sentry-install.js:1
    newValue moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:10535
    send moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    get moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    default moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-6.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    internalRequire moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:10966
    runModule moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11357
    entryExports moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11347
    loadBundle moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11346
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
Uncaught (in promise) Error: No response from RPC
runtime-lavamoat.js:8939:17
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    InterpretGeneratorResume self-hosted:1458
    AsyncFunctionNext self-hosted:668
    (Async: async)
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    default moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-6.js:1
    send moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    a moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/sentry-install.js:1
    (Async: setTimeout handler)
    a moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/sentry-install.js:1
    apply self-hosted:2705
    newValue moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:10535
    send moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    get moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    default moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-6.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    AsyncFunctionNext self-hosted:668
    (Async: async)
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    internalRequire moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:10966
    runModule moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11357
    entryExports moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11347
    map self-hosted:180
    loadBundle moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11346
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1

​

Version

10.18.3

Build type

No response

Browser

Firefox

Operating system

Windows

Hardware wallet

No response

Additional context

I shouldn't be effectivly locked out of my wallet if the RPC is down, I can't even change the RPC now.

JABirchall commented 1 year ago

Screenshot for context

JABirchall commented 1 year ago

Ive had to completly remove metamask and reinstall it again to be able to change RPC.

The and orginal RPC wasnt even down, it was working fine. dont know why metamask giving error the rpc was not responding.

bschorchit commented 1 year ago

Possibly related to https://github.com/MetaMask/metamask-extension/issues/9196

cinjon commented 1 year ago

I'm running into this as well when testing with wdio. Sometimes it will work, most of the time I get the following error as shown in the screenshot.

This is on Chrome 104.0.5112.101 and Metamask 10.18.3.

Screen Shot 2022-08-27 at 2 18 53 PM

.

cinjon commented 1 year ago

What is metamask using to do automated web integration tests? I have a reasonably small wdio setup that fails ~80% of the time due to this issue. (cc @bschorchit)

cinjon commented 1 year ago

@JABirchall Any chance you figured this out?

iteyelmp commented 1 year ago
image

Is there any solution to this problem? I get this error when I execute transactions synchronously in batches. After an error occurs, shutting down and restarting, and closing the browser will not work. You can only uninstall and reinstall.

iteyelmp commented 1 year ago

10 batch tasks are bound to trigger the error.

JABirchall commented 1 year ago

@JABirchall Any chance you figured this out?

Nope, uninstalling and reinstalling metamask fixed the issue. So maybe its a longeverty thing. Something (logs, data, vault, transcation, etc) gets too big and metamask cant load because of it. I had been using metamask for about 3 years before this error happened.

Sorry for late reply, but since i had fixed it by reinstalling i didnt bother replying.

iteyelmp commented 1 year ago

OK, thanks. But the wallet of the dapp user cannot be deleted. So I don't know how to fix this problem.

hongda3141 commented 1 year ago

same story in my linux : Screenshot from 2023-03-27 07-17-53 and log: Screenshot from 2023-03-27 07-29-45

every time I must restart, it will work, but I have some auto login code that must success for not restart, how to fix this "had trouble starting" error?

smichea commented 1 year ago

same pb here on win11 , the extension never loads and definitely cannot uninstall

JABirchall commented 1 year ago

Yea, i suppose this is a big issue for some people since they havnt backed up their seed and cant just uninstall/reinstall to fix the problem.

smichea commented 1 year ago

I have the password and private key but this procedure doesnt help to recover the seed. because of the failure to load when you try the command

chrome.storage.local.get('data', result => {
 var vault = result.data.KeyringController.vault
 console.log(vault)
})

you get 


Uncaught Error: LavaMoat - property "chrome" of globalThis is inaccessible under scuttling mode. To learn more visit https://github.com/LavaMoat/LavaMoat/pull/360.
``
linuxh3lper commented 1 year ago

I have the password and private key but this procedure doesnt help to recover the seed. because of the failure to load when you try the command

chrome.storage.local.get('data', result => {
 var vault = result.data.KeyringController.vault
 console.log(vault)
})

you get

Uncaught Error: LavaMoat - property "chrome" of globalThis is inaccessible under scuttling mode. To learn more visit https://github.com/LavaMoat/LavaMoat/pull/360.
``

Hi smichea, when you use firefox... see this guide: https://community.metamask.io/t/metamask-blank-screen-on-firefox-but-no-seed/12971/32

noxonsu commented 1 year ago

same problem

ui-10.js:26 Error: No response from RPC
  at ui-10.js:1:228215
  at e.<computed> (sentry-install.js:1:682)
  at s (sentry-install.js:1:13706)
_ @ ui-10.js:26
runtime-lavamoat.js:7100 SES_UNHANDLED_REJECTION: Error: No response from RPC
  at ui-10.js:1:228215
  at e.<computed> (sentry-install.js:1:682)
  at s (sentry-install.js:1:13706)
handleRejection @ runtime-lavamoat.js:7100
finalizeDroppedPromise @ runtime-lavamoat.js:6928
rodrigoaguilera commented 1 year ago

I have been affected by this bug. What worked for me is inspecting the sqlite db for the id column in the file table then decreasing the fnumber in the filename accordingly. A firefox restart and metamask is working again As described here https://github.com/MetaMask/metamask-extension/issues/9196

JABirchall commented 1 year ago

I have been affected by this bug. What worked for me is inspecting the sqlite db for the id column in the file table then decreasing the fnumber in the filename accordingly. A firefox restart and metamask is working again As described here #9196

Thats a different issue.

shadybuffet commented 1 year ago

i am having the same issue as above ror: No response from RPC at ui-10.js:1:160842 at e. (sentry-install.js:1:693) at s (sentry-install.js:1:13756) e. @ sentry-install.js:1 (anonymous) @ sentry-install.js:76 E @ ui-11.js:26 await in E (async) (anonymous) @ ui-11.js:26 (anonymous) @ ui-7.js:1 (anonymous) @ ui-10.js:1 e. @ sentry-install.js:1 s @ sentry-install.js:1

is there any solution to this problem, it is a browser extension

Update: fixed it I was able to fix this by removing and reinstalling the extension and for those who did not save their recovery phase (provided you are using a browser extension)

follow these steps here:

1 https : //support.metamask.io/hc/en-us/articles/360018766351-How-to-use-the-Vault-Decryptor-with-the-MetaMask-Vault-Data

2 https : //support.metamask.io/hc/en-us/articles/360015489271-How-to-add-missing-accounts-after-restoring-with-Secret-Recovery-Phrase

Thnx

lebed2045 commented 11 months ago

same issue,

image
nisdas commented 11 months ago

Is there any update on this, or recovery steps that we can do to get metamask working again ? I really want to avoid removing/reinstalling the extension here

JackBekket commented 11 months ago

I have the password and private key but this procedure doesnt help to recover the seed. because of the failure to load when you try the command

chrome.storage.local.get('data', result => {
 var vault = result.data.KeyringController.vault
 console.log(vault)
})

you get

Uncaught Error: LavaMoat - property "chrome" of globalThis is inaccessible under scuttling mode. To learn more visit https://github.com/LavaMoat/LavaMoat/pull/360.
``

Same problem

So how can I get access to vault if I don't want to reinstall metamask?

JABirchall commented 11 months ago

@DDDDDanica seems this is still a persistant issue affecting more users.

Any timeline for when this is going to be looked at?

sentry-io[bot] commented 10 months ago

Sentry issue: METAMASK-X6Y1

gauthierpetetin commented 10 months ago

Lowering this to a sev2 as we're not handling it as a sev1 at the moment, but we shall work on it at the beginning of Q4.

github-actions[bot] commented 7 months ago

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

JABirchall commented 7 months ago

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

There is no way metamask is getting away with this bug going ignored!

Astrit11 commented 7 months ago

I started getting this issue as well and there is no way to escape this issue I will have to uninstall and install it again but that should not be the case since I don't know seed phrase,did anyone succeeded to resolve without uninstall/install?

Btw created a new issue here: https://github.com/MetaMask/metamask-extension/issues/22355

yaerna1984 commented 6 months ago

Does it at least load when there is a response from RPC? Mine keeps spinning.

sentry-io[bot] commented 3 months ago

Sentry Issue: METAMASK-X9KC

github-actions[bot] commented 2 weeks ago

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

09306677806 commented 2 weeks ago

فعالیت دارم و زنده ام منتها منو نادیده گرفتین لطفا منو ازین حالت بیرون

بیارین شهرزاد ماهرو*#

در تاریخ یکشنبه ۷ ژوئیه ۲۰۲۴،‏ ۱۹:۳۴ github-actions[bot] < @.***> نوشت:

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

— Reply to this email directly, view it on GitHub https://github.com/MetaMask/metamask-extension/issues/15629#issuecomment-2212495083, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANEZZRBH4TJSN4YXUZI6JLDZLFRKVAVCNFSM563B2TNKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMRRGI2DSNJQHAZQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

09306677806 commented 2 weeks ago

هرچی هکر هر روز به من نفوذ میکنه بس کنید خجالت بکشید دیگه*

در تاریخ یکشنبه ۷ ژوئیه ۲۰۲۴،‏ ۲۰:۳۵ Shahrzad Mahro < @.***> نوشت:

فعالیت دارم و زنده ام منتها منو نادیده گرفتین لطفا منو ازین حالت بیرون

بیارین شهرزاد ماهرو*#

در تاریخ یکشنبه ۷ ژوئیه ۲۰۲۴،‏ ۱۹:۳۴ github-actions[bot] < @.***> نوشت:

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

— Reply to this email directly, view it on GitHub https://github.com/MetaMask/metamask-extension/issues/15629#issuecomment-2212495083, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANEZZRBH4TJSN4YXUZI6JLDZLFRKVAVCNFSM563B2TNKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMRRGI2DSNJQHAZQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>