Excellent Work!ã¢ëœâ€¦ã¢ëœâ€¦ã¢ëœâ€¦you Earned 2/3 Stars for Accuracy! ?try Again to Earn Them All Ã¢â€ Â»speed

Sometimes y'all may find yourself facing a problem that doesn't have a clear solution. These troubleshooting tips may help you solve problems you encounter.

Bug on the Substitution

INSUFFICIENT_OUTPUT_AMOUNT

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

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

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

1 .

Refresh your page and try again later.
2 .

Try trading a smaller amount at in one case.
3 .
Increase your slippage tolerance:
1. 1 .
  
  Tap the settings icon on the liquidity page.
2. two .
  
  Increase your slippage tolerance a little and try over again.
4 .

Lastly, try inputting an amount with fewer decimal places.

This normally happens when trading tokens with depression liquidity.

That means at that place isn't enough of ane of the tokens y'all're trying to swap in the Liquidity Pool: it'south probably a small-cap token that few people are trading.

Still, there's too the chance that you're trying to trade a scam token which cannot exist sold. In this example, PancakeSwap isn't able to block a token or return funds.

INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

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

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

Refresh your folio and try again, or effort again subsequently.

one .

Tap the settings icon on the liquidity page.
2 .

Increase your slippage tolerance a fiddling and effort over again.

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

It might exist the case that prices are updating too fast when and your slippage tolerance is too depression.

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

There currently isn't a simple style to solve this result from the PancakeSwap website: you'll need to interact with the contract straight. You tin add together liquidity directly via the Router contract, while setting amountAMin to a modest amount, then withdrawing all liquidity.

Approve the LP contract

1 .

Select Write Contract , and then Connect to Web3 and connect your wallet.
2 .
In section "1. approve", approve the LP token for the router by inbound
1. 1 .
  
  spender (address): enter the contract address of the LP token you're trying to interact with

Query "balanceOf"

2 .

In 5. balanceOf , input your wallet accost and hitting Query .
3 .

Proceed track of the number that's exported. It shows your rest within the LP in the uint256 format, which yous'll need in the side by side step.

Add or Remove Liquidity

1 .

Select Write Contract and Connect to Web3 as above.
2 .

Observe addLiquidity or removeLiquidity (whichever 1 you lot're trying to do)
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" higher up.
five .

Set a depression amountAMin or amountBMin : endeavour 1 for both.
6 .

Add together your wallet address in to (address) .
seven .

Borderline must exist an epoch fourth dimension greater than the time the tx is executed.

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

PancakeRouter: EXPIRED

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

Try again, but confirm (sign and circulate) the transaction equally soon as you generate it.

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

Pancake: G

The transaction cannot succeed due to error: Pancake: G. This is probably an issue with ane of the tokens you are swapping.

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

This usually happen when you are trying to swap a token with its own fee.

Pancake: TRANSFER_FAILED

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

Brand sure you have 30% more tokens in your wallet than you intend to trade, or try to merchandise a lower amount. If you desire to sell the maximum possible, try seventy% or 69% instead of 100%. Caused by the design of Restorative Rebase tokens like tDoge or tBTC. Sympathize how restorative rebase tokens work .

Another possible cause of this issue is the malicious token issuer just suspended the trading for their token. Or they made selling activity but possible for selected wallet addresses. Please ever exercise your own enquiry to avoid whatsoever potential fraud. If the token you are trying to swap but failed with this mistake code is coming from an airdrop, that is most likely a scam. Delight do not perform any token blessing or follow any links, your fund may exist at risk if you effort to do and so.

Transaction cannot succeed

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

Price Touch on too Loftier

Endeavor trading a smaller corporeality, or increase slippage tolerance via the settings icon and try again. This is caused past depression liquidity.

estimateGas failed

This transaction would neglect. Please contact back up

If you got this fault while removing liquidity from a BNB pair:

Please select "Receive WBNB" and retry.

If you got this error while trying to swap:

Please contact the project team of the token you're trying to bandy. **** This issue must be resolved by the project team.

This issue (while swapping) is acquired by tokens which take 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 affected will likely not work with the V2 router: they will well-nigh probable need to create new versions of their tokens pointing to our new router address, and migrate whatever existing token holders to their new token.

Nosotros recommend that any projects which created such tokens should also make efforts to forbid 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 error has been reported on mobile devices using Trust Wallet.

1 .

Try the transaction once again with increased slippage allowance.
2 .

If ane. does not resolve your problem, consider using another wallet such as SafePal for your transaction.

This usually happens when trading tokens with bereft slippage allowance on Trust Wallet.

The verbal 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 bandy tokens, the transaction fails and this error bulletin is displayed. This error has been reported across platforms.

1 .

Check to brand sure you take sufficient funds available.
ii .

Ensure you have given the contract allowance to spend the amount of funds yous're attempting to trade with.

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

Issues with Syrup Pools

BEP20: burn down amount exceeds residue

Fail with mistake 'BEP20: fire amount exceeds remainder'

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

Become at to the lowest degree equally much SYRUP as the amount of Block that you're trying to unstake.

1 .

Purchase SYRUP on the exchange. If you desire to unstake 100 Block, you need at least 100 SYRUP.

If that still fails, you can perform an "emergencyWithdraw" from the contract direct to unstake your staked tokens.

2 .

Click "Connect to Web3" and connect your wallet.
three .

In department "four. emergencyWithdraw" , enter "0" and click "Write".

This volition unstake your staked tokens and lose any uncollected Block yield.

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

To finish this happening again, don't sell your SYRUP. You still demand it to unstake from the "Stake Cake Earn Block" pool.

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

Out of Gas mistake

Warning! Error encountered during contract execution [out of gas]

You take set a depression gas limit when trying to make a transaction.

Attempt manually increasing the gas limit (not gas toll!) in your wallet earlier signing the transaction.

A limit of 200000 is usually plenty.

The to a higher place instance is from Metamask; check your wallet's documentation if yous aren't sure how to adjust the gas limit.

Basically, your wallet (Metamask, Trust Wallet, etc.) tin't finish what information technology'southward trying to do.

Your wallet estimates that the gas limit is as well low, so the role call runs out of gas before the office telephone call is finished.

BEP20: transfer corporeality exceeds allowance

Fail with mistake 'BEP20: transfer amount exceeds allowance'

1 .

Employ Unrekt.net to revoke approving for the smart contract you're trying to interact with
2 .

Approve the contract once again, without setting a limit on spend allowance
3 .

Effort interacting with the contract again.

This happens when yous set a limit on your spend allowance when you beginning approved the contract, then endeavour to swap more than the limit.

BEP20: transfer corporeality exceeds residual

Fail with error 'BEP20: transfer corporeality exceeds balance'

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

If not, you may be trying to send tokens that you don't have in your wallet (for case, trying to send a token that is already assigned to a pending transaction). In this instance, just make sure you have the tokens you're trying to use.

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

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

1 .

Find the contract address of the Syrup Pool yous're trying to unstake from. You lot can find it in your wallet'south transaction log.
4 .

Click "Connect to Web3" and connect your wallet.
5 .

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

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

This volition lose whatsoever yield that you haven't harvested notwithstanding.

This error tends to announced when you lot're trying to unstake from an old Syrup Pool, merely there aren't enough rewards in the puddle left for y'all to harvest when withdrawing. This causes the transaction to fail.

Issues with Prediction

Other issues

Provider Error

Provider Fault No provider was plant

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

Unsupported Chain ID

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

Already processing eth_requestAccounts. Delight expect.

Make sure you are signed in to your wallet app and it'southward connected to BNB Smart Concatenation.

Problems ownership SAFEMOON and like tokens

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

five% fee = redistributed to all existing holders
5% fee = used to add liquidity

This is too why you lot might not receive every bit much of the token equally you expect when yous buy. Read more than on How to Buy Safety Moon .

Internal JSON-RPC errors

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

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

Internal JSON-RPC error. { "code": -32000, "bulletin": "insufficient funds for transfer" } - Delight try again.

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

Mistake: [ethjs-query]

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

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

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

Cause unclear. Try these steps before trying again:

Issues with Contour

Oops! We couldn't detect any Pancake Collectibles in your wallet.

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

Clear the enshroud and retry.
Retry on unlike browser.
Retry on different wallet apps.
Retry on the different network (switch between Wi-Fi and cellular)

Checking username keeps spinning

At that place are two possible causes.

1 .

You accept multiple wallets installed on the browser.

Root cause: Y'all have multiple wallets installed on the browser. It may brand a disharmonize between wallets. This is out of PancakeSwap's control and nosotros tin can do zippo.

1 .

Take simply unmarried wallet installed on browser, remove the others.
two .

Reconnect the wallet and retry setting username over again.

Root cause: Network is unstable.

1 .

Delete whatever has been entered in the text field completely.
ii .

Re-type username, then please expect for seconds.
3 .

If it doesn't work, reload the page and retry again.

whitewatiod.blogspot.com

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