SSL error: The certificate authority is not trusted

[coomac]

Describe the bug
This error message appears when I try to use the built in browser on metamask android to visit any website:

Oops! something went wrong...
We weren't able to load that page.
Reason: SSL error: The certificate authority is not trusted.

Screenshot

To Reproduce

1. Open metamask
2. Click on menu and select Browser
3. Page loads for a second and immediately refreshes to show the error.
   The error appears on the homepage (https://home.metamask.io) as well as on any other website manually typed into the address bar. No websites can be accessed because the error cannot be bypassed.

Expected behavior
Website should load without an error.

Smartphone (please complete the following information):

• Device: OnePlus 6
• OS: Android 11, custom rom (Evolution) with Nov 5 Android security update
• App Version - v1.0.7 (40)

Not sure if this is a problem introduced with the Nov 19 metamask update or from the rom (both were installed around the same time). I have noticed other wallets that are somewhat incompatible with various roms running the Nov security update.

---

to be added after bug submission by internal support / PM
Severity

• How critical is the impact of this bug on a user?
• Add stats if available on % of customers impacted
• Is this visible to all users?
• Is this tech debt?

[omnat]

Hi @coomac thanks for reporting. Could you try closing all tabs you might have open in your MetaMask browser, quit the app, and try again?
Which sites have you tried accessing that are giving this error?

[coomac]

Thanks for getting back to me. I switched to a different rom (also based on AOSP from Nov 5) and the error vanished. The bug report can be closed. If the error appears again in the future with a different rom, I will try to do more digging. To answer your question though, I had tried the sites for uniswap, balancer, zapper, yearn finance, bbc and google. Also, troubleshooting-wise, I had closed all metamask tabs, cleared the browser history and cookies within metamask, cleared the app cache/storage in android settings, wiped dalvik in twrp, reinstalled the app, and changed my web view app with no luck.

[sharpshark02020]

Is there any solutiom to this? I have this same issue on metamask app on different devices these 2 days and I didn't root any of my devices. Thamks

[coomac]

Is there any solutiom to this? I have this same issue on metamask app on different devices these 2 days and I didn't root any of my devices. Thamks

Are you using a pihole or some other system-wide adblocker? In my case, my adblocker was blocking a url related to the certificate (only made the connection because a somewhat similar issue popped up when logging in on another app). I just switched block lists.

[sharpshark02020]

Make sense. However, I never installed such app in my devices.
1 thing I noticed is, the problem occurs at the same time on both the devices. Some updates might push to metamask app, not sure.

What do you mean by switching block lists, and where did you do that?

[coomac]

I was using Adaway at the time and had to disable one of the adblock lists in the app. Don't recall which list since I now use Next DNS.

Does the error show up randomly but the websites work at other times? Also, do you get the same error on both devices at the same time regardless of if they're connected to data, your home wifi, work or some random cafe wifi?

[derek2035]

I'm debugging my local DAPP. I use the HTTPS certificate generated locally by mkcert, which also reports this error. Is there a way to solve it, thank you

[lxjwlt]

I have tried to modify some code underneath and recompiled, it works fine finally:

  <base-config cleartextTrafficPermitted="false">
    <trust-anchors>
      <certificates src="system" />
      <certificates src="user" />
    </trust-anchors>
  </base-config>

you guys could download this recompiled apk from here, only for development.

[royaldragonit]

Hey everyone.
I'm make sure 100% this error only show in android device.
To the fix problem, you need re-configure ssl for your domain.
Can general at here .
I tried and working.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity. If you feel this was closed in error please reopen and provide evidence on the current production app. Thank you for your contributions.