Please Try Again but Only if You Trust This Site

Common error messages. Use the sidebar ➡️to jump to the fault you're seeing.

Sometimes yous may find yourself facing a problem that doesn't have a clear solution. These troubleshooting tips may help you solve problems you run into.

Bug on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

The transaction cannot succeed due to fault: PancakeRouter: INSUFFICIENT_OUTPUT_AMOUNT. This is probably an issue with 1 of the tokens you lot are swapping.

the transaction cannot succeed due to fault: execution reverted: pancakerouter: insufficient_output_amount.

You're trying to swap tokens, but your slippage tolerance is besides low or liquidity is too low.

i .

Refresh your page and attempt again later on.

ii .

Try trading a smaller amount at one time.

iii .

Increment your slippage tolerance:

one .

Tap the settings icon on the liquidity page.

2 .

Increase your slippage tolerance a little and effort over again.



​

4 .

Lastly, endeavour inputting an amount with fewer decimal places.

This usually happens when trading tokens with low liquidity.

That ways there isn't plenty of one of the tokens you're trying to bandy in the Liquidity Pool: it's probably a small-scale-cap token that few people are trading.

Still, there's also the chance that you're trying to trade a scam token which cannot be sold. In this case, PancakeSwap isn't able to cake a token or return funds.

INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

Neglect with error 'PancakeRouter: INSUFFICIENT_A_AMOUNT' or Fail with mistake 'PancakeRouter: INSUFFICIENT_B_AMOUNT'

You're trying to add together/remove liquidity from a liquidity puddle (LP), but in that location isn't enough of one of the two tokens in the pair.

Refresh your page and try over again, or try again afterward.

1 .

Tap the settings icon on the liquidity page.

2 .

Increase your slippage tolerance a footling and attempt again.

The fault is caused by trying to add or remove liquidity for a liquidity pool (LP) with an bereft corporeality of token A or token B (i of the tokens in the pair).

It might be the instance that prices are updating also fast when and your slippage tolerance is also depression.

OK, so you're really adamant to fix this. We really don't recommend doing this unless you lot know what yous're doing.

In that location currently isn't a simple way to solve this issue from the PancakeSwap website: y'all'll need to interact with the contract directly. You can add together liquidity directly via the Router contract, while setting amountAMin to a small amount, then withdrawing all liquidity.

Approve the LP contract

i .

Select Write Contract , then Connect to Web3 and connect your wallet.



​

ii .

In section "1. approve", approve the LP token for the router past entering

one .

spender (address): enter the contract address of the LP token y'all're trying to interact with

Query "balanceOf"

2 .

In 5. balanceOf , input your wallet address and hit Query .

3 .

Keep track of the number that'south exported. It shows your residue within the LP in the uint256 format, which you'll need in the next step.

Add or Remove Liquidity

ane .

Select Write Contract and Connect to Web3 as above.

2 .

Find addLiquidity or removeLiquidity (whichever i you lot're trying to exercise)

3 .

Enter the token addresses of both of the tokens in the LP.

4 .

In liquidity (uint256), enter the uint256 number which you got from "balanceOf" above.

v .

Fix a low amountAMin or amountBMin : endeavor ane for both.

half dozen .

Add your wallet address in to (address) .

vii .

Borderline must be an epoch time greater than the time the tx is executed.

This tin can cause very high slippage, and can cause the user to lose some funds if frontrun

PancakeRouter: EXPIRED

The transaction cannot succeed due to fault: PancakeRouter: EXPIRED. This is probably an issue with one of the tokens you are swapping.

Endeavor again, simply confirm (sign and circulate) the transaction every bit soon equally you generate it.

This happened because you lot started making a transaction, but you didn't sign and broadcast it until it was by the deadline. That means you lot didn't hit "Confirm" quickly enough.

Pancake: K

The transaction cannot succeed due to error: Pancake: K. This is probably an issue with one of the tokens yous are swapping.

Endeavor modifying the amount on "To" field. Therefore putting "(estimated)" symbol on "From". Then initiate the swap immediately.

This normally happen when you are trying to bandy a token with its own fee.

Pancake: TRANSFER_FAILED

The transaction cannot succeed due to error: execution reverted: Pancake: TRANSFER_FAILED.

Make sure you have 30% more tokens in your wallet than you intend to trade, or attempt to trade a lower corporeality. If yous want to sell the maximum possible, try seventy% or 69% instead of 100%. Caused by the design of Restorative Rebase tokens like tDoge or tBTC. Understand how restorative rebase tokens work .

Another possible cause of this outcome is the malicious token issuer just suspended the trading for their token. Or they made selling action only possible for selected wallet addresses. Please ever practice your own inquiry to avoid any potential fraud. If the token you are trying to swap only failed with this error code is coming from an airdrop, that is most likely a scam. Please practice not perform any token approving or follow any links, your fund may be at chance if you try to exercise then.

Transaction cannot succeed

Attempt trading a smaller amount, or increment slippage tolerance via the settings icon and try again. This is caused by low liquidity.

Cost Touch on besides High

Attempt trading a smaller amount, or increase slippage tolerance via the settings icon and try again. This is caused by low liquidity.

estimateGas failed

This transaction would fail. Please contact support

If yous got this error while removing liquidity from a BNB pair:

Please select "Receive WBNB" and retry.

If y'all got this error while trying to swap:

Please contact the project squad of the token you're trying to swap. **** This outcome must exist resolved by the project team.

This issue (while swapping) is caused by tokens which accept hard-coded the V1 PancakeSwap router into their contract.

While this practice is ill-advised at best, the reason for these projects having done this appears to be due to their tokenomics, in which each purchase sends a % of the token to LPs.

The projects afflicted will probable not piece of work with the V2 router: they will most probable demand to create new versions of their tokens pointing to our new router address, and migrate any existing token holders to their new token.

Nosotros recommend that whatever projects which created such tokens should also make efforts to prevent their users from adding them to V2 LP.

Cannot read property 'toHexString' of undefined

"Unknown fault: "Cannot read property 'toHexString' of undefined"

When trying to swap tokens, the transaction fails and this error message is displayed. This fault has been reported on mobile devices using Trust Wallet.

one .

Endeavor the transaction again with increased slippage allowance.

2 .

If 1. does not resolve your problem, consider using some other wallet such as SafePal for your transaction.

This unremarkably happens when trading tokens with insufficient slippage allowance on Trust Wallet.

The exact details of the problem are still being investigated.

Execution reverted: TransferHelper: TRANSFER_FROM_FAILED.

The transaction cannot succeed due to error: execution reverted: TransferHelper: TRANSFER_FROM_FAILED.

When trying to swap tokens, the transaction fails and this fault message is displayed. This error has been reported across platforms.

one .

Bank check to brand sure you have sufficient funds available.

two .

Ensure yous have given the contract allowance to spend the corporeality of funds y'all're attempting to trade with.

This mistake happens when trading tokens with bereft allowance, or when a wallet has insufficient funds. If you're trading tokens with Restorative Rebase similar tau assets tDoge or tBTC, make sure you empathize how they work first with this guide to Rebase tokens .

Bug with Syrup Pools

BEP20: fire corporeality exceeds balance

Neglect with mistake 'BEP20: fire amount exceeds balance'

You don't take enough SYRUP in your wallet to unstake from the Cake-CAKE pool.

Get at least as much SYRUP as the amount of CAKE that you lot're trying to unstake.

1 .

Buy SYRUP on the exchange. If you want to unstake 100 CAKE, y'all demand at least 100 SYRUP.

If that however fails, you lot can perform an "emergencyWithdraw" from the contract directly to unstake your staked tokens.

2 .

Click "Connect to Web3" and connect your wallet.



​

3 .

In section "4. emergencyWithdraw" , enter "0" and click "Write".

This will unstake your staked tokens and lose any uncollected Cake yield.

This will lose whatsoever yield that you haven't harvested yet.

To stop this happening again, don't sell your SYRUP. You still need it to unstake from the "Pale Block Earn CAKE" puddle.

This error has happened because you lot accept sold or transferred SYRUP tokens. SYRUP is minted in a 1:ane ratio to Cake when you stake in the Cake-Block Syrup Puddle. SYRUP must be burned at a 1:1 ratio to Cake when calling leaveStaking (unstaking your CAKE from the pool), so if you don't have enough, y'all can't unstake from the pool.

​

​

Out of Gas error

Alarm! Mistake encountered during contract execution [out of gas]

Yous have set a depression gas limit when trying to brand a transaction.

Endeavor manually increasing the gas limit (non gas cost!) in your wallet earlier signing the transaction.

A limit of 200000 is usually enough.

The higher up instance is from Metamask; check your wallet'southward documentation if you aren't sure how to conform the gas limit.

Basically, your wallet (Metamask, Trust Wallet, etc.) can't finish what it's trying to practise.

Your wallet estimates that the gas limit is too depression, so the function telephone call runs out of gas before the function call is finished.

BEP20: transfer amount exceeds assart

Fail with error 'BEP20: transfer corporeality exceeds allowance'

1 .

Use Unrekt.net to revoke approval for the smart contract you're trying to interact with

ii .

Corroborate the contract again, without setting a limit on spend assart

3 .

Attempt interacting with the contract again.

This happens when y'all set a limit on your spend allowance when yous commencement approved the contract, and so try to bandy more than the limit.

BEP20: transfer amount exceeds balance

Fail with fault 'BEP20: transfer amount exceeds balance'

Yous're probably trying to unstake from a Syrup Puddle with low rewards in it. Solution below.

If non, you may be trying to send tokens that you don't accept in your wallet (for instance, trying to send a token that is already assigned to a pending transaction). In this example, merely make sure you have the tokens you're trying to employ.

Firstly, allow the squad know which puddle you lot're trying to unstake from, so they can top upwardly the rewards. If yous're in a hurry to unstake and yous don't mind losing your awaiting yield, try an emergencyWithdraw:

You can perform an "emergencyWithdraw" from the contract directly to unstake your staked tokens.

ane .

Find the contract accost of the Syrup Pool you're trying to unstake from. You can detect it in your wallet'due south transaction log.

4 .

Click "Connect to Web3" and connect your wallet.



​

5 .

In section "three. emergencyWithdraw", and click "Write".

This will unstake your staked tokens and lose whatever uncollected yield.

This will lose any yield that you haven't harvested still.

This error tends to appear when you're trying to unstake from an old Syrup Puddle, but in that location aren't enough rewards in the pool left for you to harvest when withdrawing. This causes the transaction to neglect.

Bug with Prediction

Other issues

Provider Error

Provider Error No provider was found

This happens when y'all try to connect via a browser extension like MetaMask or Binance Chain Wallet, but you haven't installed the extension.

Unsupported Chain ID

Switch your chain to BNB Smart Chain. Check your wallet's documentation for a guide if you need aid.

Already processing eth_requestAccounts. Please look.

Make certain yous are signed in to your wallet app and it's connected to BNB Smart Chain.

Problems ownership SAFEMOON and similar tokens

To trade SAFEMOON, y'all must click on the settings icon and prepare your slippage tolerance to 12% or more. This is because SafeMoon taxes a 10% fee on each transaction :

five% fee = redistributed to all existing holders

5% fee = used to add liquidity

This is also why you might not receive as much of the token as you wait when you buy. Read more on How to Buy Safety Moon .

Internal JSON-RPC errors

"MetaMask - RPC Fault: Internal JSON-RPC error. estimateGas failed removeLiquidityETHWithPermitSupportingFeeOnTransferTokens estimateGas failed removeLiquidityETHWithPermit "

Happens when trying to remove liquidity on some tokens via Metamask. Root crusade is still unknown. Endeavor using an alternative wallet.

Internal JSON-RPC mistake. { "code": -32000, "message": "insufficient funds for transfer" } - Please effort again.

You lot don't take enough BNB to pay for the transaction fees. You demand more BEP-20 network BNB in your wallet.

Fault: [ethjs-query]

Error: [ethjs-query] while formatting outputs from RPC '{"value":{"lawmaking":-32603,"data":{"lawmaking":-32000,"message":"transaction underpriced"}}}"

Increment the gas limit for the transaction in your wallet. Check your wallet's documentation to learn how to increase gas limit.

Swap failed: Error: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"code":-32603,"message":"handle asking error"}}}'

Cause unclear. Endeavour these steps before trying again:

Problems with Profile

Oops! Nosotros couldn't find any Pancake Collectibles in your wallet.

We're investigating the logic behind this consequence. Meanwhile delight try the workaround.

Clear the cache and retry.

Retry on unlike browser.

Retry on different wallet apps.

Retry on the unlike network (switch between Wi-Fi and cellular)

Checking username keeps spinning

There are two possible causes.

1 .

You have multiple wallets installed on the browser.

Root cause: You have multiple wallets installed on the browser. It may make a conflict betwixt wallets. This is out of PancakeSwap's command and we can do cipher.

1 .

Have but unmarried wallet installed on browser, remove the others.

ii .

Reconnect the wallet and retry setting username again.

Root cause: Network is unstable.

1 .

Delete whatever has been entered in the text field completely.

two .

Re-type username, then please wait for seconds.

3 .

If it doesn't work, reload the folio and retry once more.

mcknightasherettle36.blogspot.com

Source: https://docs.pancakeswap.finance/help/troubleshooting

Share this post