Your Session Has Expired. Please Sign in Again by Clicking on the Amazon Pay Button.

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

Bug on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

The transaction cannot succeed due to error: PancakeRouter: INSUFFICIENT_OUTPUT_AMOUNT. This is probably an issue with i of the tokens y'all are swapping.

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

You're trying to bandy tokens, only your slippage tolerance is also low or liquidity is too low.

1 .

Refresh your page and try again afterward.
two .

Try trading a smaller amount at one time.
3 .
Increase your slippage tolerance:
1. 1 .
  
  Tap the settings icon on the liquidity page.
2. two .
  
  Increase your slippage tolerance a lilliputian and try once more.
four .

Lastly, try inputting an amount with fewer decimal places.

This normally happens when trading tokens with depression liquidity.

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

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

INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

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

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

Refresh your page and try once more, or try once more later on.

1 .

Tap the settings icon on the liquidity page.
2 .

Increment your slippage tolerance a little and effort again.

The error is acquired by trying to add or remove liquidity for a liquidity puddle (LP) with an insufficient amount of token A or token B (one of the tokens in the pair).

It might be the case that prices are updating likewise fast when and your slippage tolerance is besides low.

OK, so you're really determined to gear up this. Nosotros actually don't recommend doing this unless you know what you're doing.

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

Corroborate the LP contract

i .

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

Query "balanceOf"

2 .

In five. balanceOf , input your wallet address and hit Query .
three .

Go along track of the number that's exported. It shows your balance within the LP in the uint256 format, which you'll need in the next step.

Add or Remove Liquidity

one .

Select Write Contract and Connect to Web3 as in a higher place.
two .

Find addLiquidity or removeLiquidity (whichever ane you're trying to do)
three .

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

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

Set up a low amountAMin or amountBMin : try i for both.
6 .

Add your wallet address in to (address) .
7 .

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

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

PancakeRouter: EXPIRED

The transaction cannot succeed due to error: PancakeRouter: EXPIRED. This is probably an outcome with ane of the tokens yous are swapping.

Endeavor once again, simply confirm (sign and broadcast) the transaction as soon as you generate information technology.

This happened considering you started making a transaction, but you didn't sign and broadcast it until it was past the deadline. That means y'all didn't hit "Confirm" speedily plenty.

Pancake: K

The transaction cannot succeed due to error: Pancake: K. This is probably an issue with 1 of the tokens y'all are swapping.

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

This unremarkably happen when you lot 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 accept 30% more tokens in your wallet than you intend to trade, or endeavour to trade a lower amount. If you lot want to sell the maximum possible, try 70% or 69% instead of 100%. Caused by the blueprint of Restorative Rebase tokens like tDoge or tBTC. Understand how restorative rebase tokens piece of work .

Another possible cause of this issue is the malicious token issuer just suspended the trading for their token. Or they fabricated selling action just possible for selected wallet addresses. Please always practise your own enquiry to avoid whatever potential fraud. If the token yous are trying to bandy but failed with this error code is coming from an airdrop, that is virtually probable a scam. Delight practice not perform any token blessing or follow whatsoever links, your fund may exist at chance if y'all try to do so.

Transaction cannot succeed

Try trading a smaller corporeality, or increment slippage tolerance via the settings icon and try once again. This is acquired by low liquidity.

Price Impact also High

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

estimateGas failed

This transaction would neglect. Delight contact support

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 bandy:

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

This issue (while swapping) is caused by tokens which have 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 buy sends a % of the token to LPs.

The projects affected will likely not work with the V2 router: they will most likely need to create new versions of their tokens pointing to our new router address, and drift any existing token holders to their new token.

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

Cannot read holding 'toHexString' of undefined

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

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

ane .

Attempt the transaction again with increased slippage allowance.
2 .

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

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

The exact details of the trouble are nonetheless beingness investigated.

Execution reverted: TransferHelper: TRANSFER_FROM_FAILED.

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

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

1 .

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

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

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

Issues with Syrup Pools

BEP20: burn amount exceeds rest

Fail with fault 'BEP20: fire amount exceeds remainder'

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

Become at to the lowest degree as much SYRUP every bit the amount of CAKE that yous're trying to unstake.

1 .

Buy SYRUP on the exchange. If you want to unstake 100 Cake, you need at least 100 SYRUP.

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

2 .

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

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

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

This volition lose any yield that yous haven't harvested yet.

To cease this happening once more, don't sell your SYRUP. You still demand it to unstake from the "Stake Block Earn Block" puddle.

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

Out of Gas error

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

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

Try manually increasing the gas limit (not gas price!) in your wallet before signing the transaction.

A limit of 200000 is usually enough.

The above case is from Metamask; check your wallet's documentation if you aren't sure how to adjust the gas limit.

Basically, your wallet (Metamask, Trust Wallet, etc.) tin can't end what it'south trying to exercise.

Your wallet estimates that the gas limit is besides low, so the function phone call runs out of gas before the function call is finished.

BEP20: transfer amount exceeds assart

Fail with error 'BEP20: transfer amount exceeds assart'

i .

Apply Unrekt.internet to revoke approval for the smart contract yous're trying to interact with
2 .

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

Try interacting with the contract again.

This happens when you set a limit on your spend allowance when you outset canonical the contract, then try to swap more than than the limit.

BEP20: transfer corporeality exceeds balance

Fail with error 'BEP20: transfer corporeality exceeds residual'

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

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

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

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

1 .

Find the contract address of the Syrup Pool y'all're trying to unstake from. Y'all tin can find it in your wallet's transaction log.
4 .

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

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

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

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

This error tends to appear when you're trying to unstake from an old Syrup Pool, just there aren't enough rewards in the pool left for you to harvest when withdrawing. This causes the transaction to fail.

Issues with Prediction

Other issues

Provider Mistake

Provider Error No provider was establish

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

Unsupported Chain ID

Switch your chain to BNB Smart Concatenation. Check your wallet's documentation for a guide if you demand help.

Already processing eth_requestAccounts. Please wait.

Make sure you are signed in to your wallet app and information technology's connected to BNB Smart Concatenation.

Bug buying SAFEMOON and similar tokens

To trade SAFEMOON, you must click on the settings icon and gear up your slippage tolerance to 12% or more than. This is considering SafeMoon taxes a 10% fee on each transaction :

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

This is also why you might not receive every bit much of the token as y'all expect when y'all purchase. Read more than on How to Buy Condom Moon .

Internal JSON-RPC errors

"MetaMask - RPC Error: 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" } - Please try again.

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

Error: [ethjs-query]

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

Increase the gas limit for the transaction in your wallet. Bank check your wallet's documentation to learn how to increase gas limit.

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

Cause unclear. Try these steps earlier trying again:

Issues with Profile

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

We're investigating the logic behind this result. Meanwhile delight endeavour the workaround.

Clear the enshroud and retry.
Retry on different browser.
Retry on different wallet apps.
Retry on the different 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 brand a conflict between wallets. This is out of PancakeSwap's control and we can do nothing.

1 .

Have only single wallet installed on browser, remove the others.
2 .

Reconnect the wallet and retry setting username again.

Root cause: Network is unstable.

1 .

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

Re-type username, then please wait for seconds.
iii .

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

pattersonapoing.blogspot.com

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