Solana token discovery error after Trezor Suite firmware update | Solana error #8100002

You guys seems to have broke something in 25.1.2 version update in name of providing support for Solana Token-2022.

I tried different machine, uninstall, re-install & reset of Trezor Suite app, different browsers, but could not get to load my Solana tokens. It give me the below error. I also saw tons of post in Reddit complaining the same.

@Trezor Community - Could you please add to this post if you are seeing the same?


Accounts couldn’t be loaded. If using a VPN, disable it and try again.

Solana: Solana error #8100002; Decode this error by running npx @solana/errors decode -- 8100002 'bWVzc2FnZT1Ub28lMjBNYW55JTIwUmVxdWVzdHMmc3RhdHVzQ29kZT00Mjk='


Please fix this ASAP!

6 Likes

I am having the same issue. I can see my SOL but getting this error: `npx @solana/errors decode – 8100002

I am having the same issue. Super frustrating. Sent several email to support but all I get back are self-service read docs that I have already went through. I’ve tried the web version, reset the app multiple times, and reinstalled firmware. Same error keeps coming.

I’m having the same problem. I reset my trezor and reloaded bitcoin and Solana but the Sol tokens shows an account recovery error. Is there a fix?

1 Like

Having the same issue.

Same issue here. Also not seeing the new update, I clicked “check for updates” and it says “no new updates available” even though I’m on 24.12.3. I’m on a Mac if that helps.

2 Likes

I am having the same issue. I can see my Solana.

1 Like

same issue - unable to discover/error 81000002 for solana

1 Like

My firmware and suite are up to date. I am not using a VPN. Solana assets are not showing up I get this error.


Accounts couldn’t be loaded. If using a VPN, disable it and try again.
Solana: Solana error #8100002; Decode this error by running npx @solana/errors decode -- 8100002 'bWVzc2FnZT1Ub28lMjBNYW55JTIwUmVxdWVzdHMmc3RhdHVzQ29kZT00Mjk='

2 Likes

I am having the same issue. Super frustrating. At least it comforts me that I am not alone. Hopefully they fix this very soon.

1 Like

Same issue here…discovery error, does not show any assets, I’m NOT using a VPN, tried everything, updated firmware, clear cache, custom backend server, factory reset, same error whether I’m on Trezor Suite or the Web application. Nothing helps, let’s go Trezor Team - get this fixed!!

1 Like

The error I get is:

Accounts couldn’t be loaded. If using a VPN, disable it and try again.

Solana: Solana error #8100002

1 Like

You guys seems to have broke in name of providing support for Solana Token-2022.

I tried different machine, Trezor Suite app and different browser, and could not get to load my Solana tokens. IT give the below error.

Accounts couldn’t be loaded. If using a VPN, disable it and try again.

Solana: Solana error #8100002; Decode this error by running npx @solana/errors decode -- 8100002 'bWVzc2FnZT1Ub28lMjBNYW55JTIwUmVxdWVzdHMmc3RhdHVzQ29kZT00Mjk='

Please fix this ASAP!

2 Likes

Same issue for me - solana error #81000002

I am having the same issue. Has there been any luck in restoring??

Same issue here, Solana error #8100002. Any solutions
yet?

Same issue… anxiety producing… please post your plans to remedy this error…

Solana: Solana error #8100002; Decode this error by running npx @solana/errors decode -- 8100002 'bWVzc2FnZT1Ub28lMjBNYW55JTIwUmVxdWVzdHMmc3RhdHVzQ29kZT00Mjk='

Just set up a brand new Trezor safe 3 and Initial Bitcoin wallet creation was fine but when I tried to create a solana wallet got the Discovery Error “Accounts couldn’t be loaded. If using a VPN, disable it and try again.”

Not using a VPN. Just trying to get Solana Wallet setup.

And here’s me, new Safe 5 owner. I did finally get a couple Solana tokens brought-in, on the ONE instance I could display the Solana page without error. But now it’s persistent error, regardless of eject/re-insert, close/re-launch, etc.

Solana is broken in v25.1.2.

Same issue. Are we going to get a response from support or do we just have to wait indefinitely? This downtime is unacceptable.

1 Like