Fix a stake that will not go through
A gecko you are trying to stake, unstake or restake.
What you will get out of this
- Getting a wallet to connect on a phone or a computer
- Certificate warnings and pages that will not load
- A Ledger that cancels every time
- What each staking error message means, and what to do next
Most failed stakes come down to the wallet, the network, or a transaction that landed but looked failed. Find the message you saw, then work down its steps in order.
The wallet will not connect#
On an iPhone, a browser cannot reach a wallet app on its own. Pick Phantom or Solflare in the connect window and the site reopens inside that wallet's browser. On a computer, the wallet has to be a browser extension: picking one you have not installed opens its install page. On Android, the wallet app connects straight from Chrome. If a phone keeps failing, a computer with the extension is the most reliable route.
The page will not load, or warns about the connection#
A certificate or "connection is not private" warning almost always comes from the network, not from the site. Some mobile carriers, public Wi-Fi, VPNs and filtering DNS apps intercept the connection, and the browser refuses it. This domain has no click-past button, by design.
- Switch networks: mobile data instead of Wi-Fi, or the reverse.
- Turn off any VPN, ad blocker or DNS filter, then reload.
- On Android, set Private DNS to
one.one.one.one. On a computer, try another browser. - Set the device clock to update automatically. A wrong date breaks every certificate.
- Check the address against our official links.
Still stuck? Send support the warning's error code and certificate issuer.
"Staking data unavailable"#
The page could not reach the Solana network. Press Try again, then reload. If it keeps happening, treat it as the network problem above: switch connections or turn the VPN off. "Failed to fetch Solana network time" is milder: the page uses your device clock instead, so check it is right.
A Ledger cancels every time#
A Ledger cannot sign the newer transaction format yet, and the wallet reports its refusal as a cancel. The first time, the site says so: "If you're using a Ledger, it can't sign the newer transaction format yet."
- Unlock the Ledger and open the Solana app on it.
- In the Solana app settings, turn on Blind signing.
- Press stake again within ten minutes. The site switches to the format a Ledger can sign and remembers it for this wallet.
That format stakes or unstakes one gecko per transaction, so expect one device approval per gecko.
"Transaction was cancelled"#
Reject was pressed, a prompt was closed, or a Ledger refused. Nothing was sent and nothing was charged. Staking many geckos can take several prompts: approve each one.
"This wallet has no SOL"#
Every transaction pays a small network fee in SOL. Send a little SOL to this wallet, a hundredth of one is plenty, and try again.
"The staking program rejected this transaction"#
The program refused before anything changed, so no fee was charged. The reason follows the colon. The usual ones:
- The gecko is already staked, or its journey has not ended.
- You tried to unstake your Captain while other geckos are still staked. Unstake the others first.
- A restake says the gecko "is currently locked". Wait a moment and refresh.
What each journey locks, and for how long.
"This wallet can't stake"#
Wallets known to be involved in theft of geckos are blocked from parts of this site, to protect holders from trading with them.
If you think that is a mistake, open a ticket.
Lost, expired, or "Something went wrong"#
These do not prove it failed: a busy network can land a transaction after the site stops waiting.
- Do not press stake again yet.
- Open the wallet's activity, or look the wallet up on Solscan.
- Reload the staking page and check which geckos now show as staked.
- Retry only the ones that did not land.
"Network was congested and your transaction expired" is the exception: that one never landed, so just try again.
Staking several geckos fails#
Reload first: part of the batch may have landed. Then step up: one gecko, then four, then ten, and stake the rest in batches of the largest size that worked.
Still stuck#
Open a Staking Support ticket in #support-tickets with:
- the exact message, or a screenshot of it;
- your wallet app, and whether a Ledger is attached;
- phone or computer, and which browser;
- a transaction signature, if the wallet shows one.
Never share a seed phrase or private key: support will never ask for one.