Solana error fixes

What Solana, SPL Token, Anchor and DEX program errors mean, taken from the program source, and how to fix each one.

51 pages

"Transferring, minting, and burning is paused on this mint" (Token-2022 0x3f)The token uses the Token-2022 pausable extension and its pause authority has paused it. While paused, no one can transfer, mint or burn the token, so you cannot sell.Updated 23 Oct 2026
"Transfer is disabled for this mint" (Token-2022 0x24)The token uses the Token-2022 non-transferable extension, so it can never be sent, sold or swapped from your account. This is by design for soulbound tokens, and a trap when a tradable-looking token uses it.Updated 23 Oct 2026
How to decode Solana "custom program error" codesThe hex number is an error code from the program that failed. The same number means different things in different programs, so you need both the code and the program ID.Updated 23 Oct 2026
Meteora DLMM error 6060: MissingTokenAmountAsTokenLaunchProofCreating a customizable permissionless DLMM pair requires the creator to hold the quote token, such as a wrapped SOL account with a balance above zero, as proof. Without it, creation fails.Updated 23 Oct 2026
Meteora DLMM error 6055 (0x17a7): LiquidityLockedYou tried to remove liquidity in the same slot it was added. DLMM blocks that to prevent just-in-time liquidity; it works one slot later.Updated 23 Oct 2026
Meteora DLMM slippage errors 6003 and 6004The pool price moved before your transaction ran. 6003 means the amount would fill outside your slippage; 6004 means the active bin moved further than your bin tolerance.Updated 23 Oct 2026
Raydium CPMM "Init lp amount is too less" error 6009The first deposit into a new CPMM pool is too small. Raydium locks 100 units of LP on creation, so the initial liquidity must produce more than that.Updated 24 Oct 2026
Raydium "Not support token_2022 mint extension" errorThe Token-2022 token uses an extension Raydium pools do not accept, so a pool cannot be created or traded for it.Updated 23 Oct 2026
Raydium "Exceeds desired slippage limit" (CPMM 6005, AMM v4 0x1e)A swap or deposit on a Raydium CPMM or AMM v4 pool would fill worse than your slippage limit because the pool moved first.Updated 23 Oct 2026
Raydium "Price slippage check" error 6017 (0x1781)On a Raydium concentrated (CLMM) pool, the price moved past the limit set by your slippage or price range before the instruction ran. When adding one-sided liquidity, a range that starts on the current tick also triggers it.Updated 23 Oct 2026
Jupiter error 6000 (0x1770): EmptyRoute and "no route found"Jupiter could not build a route for the pair and amount, usually because the token has little or no liquidity, the amount is too large or too small, or the pool is not indexed yet.Updated 23 Oct 2026
"custom program error: 0x1771" (6001): what it means0x1771 is the second custom error of an Anchor program, so its meaning depends on which program failed. On Jupiter, the most common source, it is SlippageToleranceExceeded.Updated 23 Oct 2026
PumpSwap error 6004 (0x1774): ExceededSlippageA trade on a PumpSwap pool would fill worse than your slippage limit because the pool price moved first. On buys sized in SOL, the same problem shows as 6040.Updated 23 Oct 2026
pump.fun error 6042 (0x179a): BuySlippageBelowMinTokensOutThe buy, sized in SOL, would return fewer tokens than the minimum your slippage setting allows, because the price rose before it ran.Updated 23 Oct 2026
pump.fun error 6040 or 6041: not enough SOL for rent or feesYour wallet has enough for the buy itself but not for the extra costs: rent for new accounts (6040) or the trading fees (6041).Updated 23 Oct 2026
pump.fun error 6005 (0x1775): BondingCurveCompleteThe coin has graduated: its bonding curve filled (85 SOL) and liquidity moved to a PumpSwap pool. The curve no longer accepts trades. The message still says Raydium, from before pump.fun moved graduations to PumpSwap.Updated 23 Oct 2026
pump.fun error 6003 (0x1773): TooLittleSolReceivedYour sell would return less SOL than your slippage limit allows, because other sellers pushed the price down first.Updated 23 Oct 2026
pump.fun error 6002 (0x1772): TooMuchSolRequiredYour buy would cost more SOL than your slippage limit allows, because other buyers moved the price on the bonding curve before your transaction ran.Updated 23 Oct 2026
Anchor error 3007 (0xbbf): AccountOwnedByWrongProgramAn account belongs to a different program than expected. The common case is a Token-2022 token passed where the original Token program is expected, or the reverse.Updated 23 Oct 2026
Anchor error 2006 (0x7d6): ConstraintSeedsAn account address does not match the address the program derives from its seeds, usually because the app passed the wrong account or derived it for the wrong mint, user or program version.Updated 23 Oct 2026
Anchor error 3012 (0xbc4): AccountNotInitializedThe program expected an account to exist but it has not been created yet, such as a token account, pool position or user state account.Updated 23 Oct 2026
"Non-native account can only be closed if its balance is zero" (0xb)You tried to close a token account that still holds tokens. Only empty token accounts can be closed to reclaim rent.Updated 23 Oct 2026
"custom program error: 0x3" (Account not associated with this Mint)The token account passed in holds a different token than the mint in the instruction, usually because an app mixed up two token accounts.Updated 23 Oct 2026
"custom program error: 0x4" (Owner does not match) fixThe token account is owned by a different wallet than the one signing. You are trying to move tokens from an account you do not control, or the app picked the wrong account.Updated 23 Oct 2026
"custom program error: 0x0" on Solana: what it meansIn the System Program, 0x0 means an account with that address already exists. In the SPL Token program, 0x0 means the account balance is below the rent-exempt threshold.Updated 23 Oct 2026
"custom program error: 0x1" on Solana: insufficient fundsIn the SPL Token program, code 0x1 means the source token account holds fewer tokens than the transfer asks for. In the System Program, code 1 means the account does not have enough SOL.Updated 23 Oct 2026
Solana RPC "429 Too Many Requests": limits and fixesYour app or wallet sent more requests than the RPC endpoint allows. The public mainnet endpoint allows 100 requests per 10 seconds per IP, 40 per 10 seconds for a single method and 40 concurrent connections.Updated 23 Oct 2026
"Signature has expired: block height exceeded" fixThe transaction did not land before its blockhash expired, usually because the network was busy or the priority fee was too low. It was never processed, so no funds moved.Updated 23 Oct 2026
Solana "transaction too large" error: the 1,232-byte limitA Solana transaction must fit in 1,232 bytes, which is the IPv6 minimum packet size of 1,280 bytes minus 48 bytes of headers. Many accounts or instructions push it over.Updated 23 Oct 2026
"Program failed to complete" on Solana: causesA program stopped mid-execution, most often because it ran out of compute units or hit an internal limit, without returning a specific error code.Updated 23 Oct 2026
"Transaction loads an address table account that doesn't exist" fixThe versioned transaction points to an address lookup table that is not on this network, was closed, or the app used a table from a different cluster.Updated 23 Oct 2026
"Account in use" on Solana: what it meansAnother transaction in the same block is already writing to an account your transaction also needs to write, so the runtime refuses to process both at once.Updated 23 Oct 2026
"Transaction contains a duplicate instruction that is not allowed" fixThe transaction includes the same compute budget instruction twice, typically because an SDK added its own compute unit limit or price and the app added another.Updated 23 Oct 2026
"Computational budget exceeded" on Solana: fixThe transaction ran out of compute units. Each instruction gets 200,000 by default and a transaction can use at most 1,400,000.Updated 23 Oct 2026
"This transaction has already been processed" on SolanaThe same signed transaction was sent twice. The first copy already landed, so the network rejects the duplicate.Updated 23 Oct 2026
"Insufficient funds for fee" on Solana: fixThe fee payer does not hold enough SOL to pay the base fee (5,000 lamports per signature) plus any priority fee the transaction sets.Updated 23 Oct 2026
"Attempt to debit an account but found no record of a prior credit" fixThe wallet paying the fee has never held SOL on this network, so the runtime cannot find it. It almost always means an empty wallet or the wrong network (devnet versus mainnet).Updated 23 Oct 2026
Blockhash not found: Solana transaction fixBlockhash not found means the transaction used a recent blockhash that the network no longer accepts, usually because it expired or your RPC is behind. Rebuild the transaction with a fresh blockhash and resend.Updated 23 Oct 2026
Cannot close account: it has withheld transfer feesA Token-2022 token account cannot be closed while it still holds withheld transfer fees. Harvest the withheld fees to the mint first, then close the account.Updated 23 Oct 2026
Insufficient funds for rent: what it meansThis error means a transaction would leave an account with less SOL than the rent-exempt minimum, or the payer cannot cover the new account rent. Add a little SOL to the paying wallet and retry.Updated 23 Oct 2026
Slippage tolerance exceeded on Solana: fixThis error means the price moved further than your slippage setting before the swap ran, so it was cancelled. Raise the tolerance a little, reduce the trade size, or retry when the price is steadier.Updated 23 Oct 2026
Axiom cannot connect to Phantom: fixAxiom's documentation does not cover Phantom connection errors. These are the standard wallet-connection checks that fix most "failed to connect" cases on Solana sites.Updated 12 Oct 2026
GMGN copy trade not working: checklistGMGN copy trades usually fail because a filter blocked the buy, the balance fell too low, slippage was too tight, or the priority fee was too low. A checklist from GMGN's docs.Updated 12 Oct 2026
Jupiter swap keeps failing: what to changeJupiter swap failures map to a few documented causes: slippage exceeded (6001), an expired blockhash, no route, insufficient funds for fees and rent, or RPC problems. What to change for each.Updated 12 Oct 2026
Phantom not working: status and fixesMatch your Phantom symptom to the fix Phantom's own help center describes: Ledger not connecting, transactions stuck pending, funds that have not arrived, or a restricted "Transactions Disabled" wallet.Updated 12 Oct 2026
Phantom transaction failed: causes and fixesPhantom transactions fail for a few documented reasons: a Ledger that is locked or has blind signing off, fees too low on EVM networks, or a restricted address. How to tell which one it is.Updated 12 Oct 2026
Photon "insufficient SOL balance": fix"Insufficient SOL balance" means the wallet cannot cover the whole transaction, not only the trade amount. What the cost includes on Photon and how much buffer to keep.Updated 12 Oct 2026
pump.fun failed to sign transaction: fix"Failed to sign transaction" on pump.fun is raised by your wallet, not the pump.fun contract. Start with the wallet connection and balance, then look at the failure causes pump.fun lists in its terms.Updated 12 Oct 2026
pump.fun transaction failed: causes and fixespump.fun's terms name the reasons an order can fail: reverted or dropped transactions, slippage, and changing network or priority fees. A checklist for each, with the fee page that explains what you are charged.Updated 12 Oct 2026
Transaction failed: account frozenAn "account is frozen" failure means the token's mint has a freeze authority and it froze your token account. Only that authority can thaw it, so check the mint before you contact anyone.Updated 23 Oct 2026
Trojan copy trade not working: checklistTrojan's docs say copy trading does not work with every wallet. A checklist from Trojan's documentation: funding, unsupported target wallets, slippage, fees, and sell settings.Updated 12 Oct 2026