I Wont Let You in Again the Messages I Tried to Send

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

Issues on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

The transaction cannot succeed due to fault: PancakeRouter: INSUFFICIENT_OUTPUT_AMOUNT. This is probably an result with one of the tokens y'all are swapping.

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

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

1 .

Refresh your page and try again subsequently.
ii .

Endeavour trading a smaller amount at one time.
three .
Increment your slippage tolerance:
1. 1 .
  
  Tap the settings icon on the liquidity page.
2. 2 .
  
  Increase your slippage tolerance a little and try again.
4 .

Lastly, attempt inputting an corporeality with fewer decimal places.

This unremarkably happens when trading tokens with low liquidity.

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

Yet, in that location's also the risk 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 error 'PancakeRouter: INSUFFICIENT_A_AMOUNT' or Fail with error 'PancakeRouter: INSUFFICIENT_B_AMOUNT'

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

Refresh your page and attempt again, or effort again afterward.

1 .

Tap the settings icon on the liquidity page.
2 .

Increase your slippage tolerance a picayune and try again.

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

Information technology might be the case that prices are updating also fast when and your slippage tolerance is as well depression.

OK, so yous're really determined to set this. Nosotros really don't recommend doing this unless you know what you lot're doing.

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

Corroborate the LP contract

1 .

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

Query "balanceOf"

ii .

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

Keep track of the number that'southward exported. It shows your balance within the LP in the uint256 format, which yous'll demand in the side by side step.

Add or Remove Liquidity

1 .

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

Find addLiquidity or removeLiquidity (whichever one you'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" above.
5 .

Set a low amountAMin or amountBMin : attempt ane for both.
6 .

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

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

This tin 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 issue with i of the tokens y'all are swapping.

Endeavour over again, only ostend (sign and broadcast) the transaction as shortly as you generate information technology.

This happened considering you lot started making a transaction, just you didn't sign and broadcast it until it was past the deadline. That means you didn't hit "Confirm" apace enough.

Pancake: K

The transaction cannot succeed due to mistake: Pancake: Thousand. This is probably an consequence with one of the tokens yous are swapping.

Try 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 fault: execution reverted: Pancake: TRANSFER_FAILED.

Make certain you have 30% more than tokens in your wallet than you intend to trade, or try to trade a lower amount. If you want to sell the maximum possible, try 70% or 69% instead of 100%. Caused by the design of Restorative Rebase tokens like tDoge or tBTC. Empathise how restorative rebase tokens piece of work .

Some other possible cause of this issue is the malicious token issuer just suspended the trading for their token. Or they made selling action but possible for selected wallet addresses. Delight e'er exercise your ain research to avoid any potential fraud. If the token you are trying to bandy only failed with this error code is coming from an airdrop, that is most likely a scam. Please practice not perform any token approval or follow any links, your fund may be at take chances if you try to do so.

Transaction cannot succeed

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

Price Touch on too Loftier

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

estimateGas failed

This transaction would fail. Please contact back up

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

Please select "Receive WBNB" and retry.

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

Please contact the projection team of the token yous're trying to swap. **** This event must be resolved by the projection squad.

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

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

The projects affected will likely non 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 calculation them to V2 LP.

Cannot read property 'toHexString' of undefined

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

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

one .

Attempt the transaction again with increased slippage allowance.
2 .

If 1. does non resolve your trouble, consider using another wallet such equally SafePal for your transaction.

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

The verbal details of the problem are nonetheless existence 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 fault message is displayed. This mistake has been reported across platforms.

1 .

Check to make certain you have sufficient funds bachelor.
2 .

Ensure you take given the contract allowance to spend the amount of funds y'all're attempting to trade with.

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

Bug with Syrup Pools

BEP20: burn corporeality exceeds residue

Fail with error 'BEP20: burn amount exceeds residuum'

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

Get at to the lowest degree as much SYRUP as the corporeality of Block that you're trying to unstake.

one .

Purchase SYRUP on the exchange. If you want to unstake 100 CAKE, you need at least 100 SYRUP.

If that even so 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 "iv. emergencyWithdraw" , enter "0" and click "Write".

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

This will lose whatever yield that you lot haven't harvested nevertheless.

To stop this happening again, don't sell your SYRUP. You lot yet demand it to unstake from the "Pale Block Earn Block" pool.

This error has happened because yous have sold or transferred SYRUP tokens. SYRUP is minted in a one:one ratio to Cake when you pale in the CAKE-CAKE Syrup Puddle. SYRUP must exist burned at a 1:1 ratio to Cake when calling leaveStaking (unstaking your Cake from the pool), and so if you don't have enough, you tin't unstake from the pool.

Out of Gas error

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

You take fix a depression gas limit when trying to brand a transaction.

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

A limit of 200000 is unremarkably enough.

The in a higher place example 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 finish what information technology's trying to practice.

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

BEP20: transfer corporeality exceeds allowance

Fail with fault 'BEP20: transfer amount exceeds allowance'

1 .

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

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

Endeavour interacting with the contract again.

This happens when yous prepare a limit on your spend allowance when you beginning approved the contract, and so effort to swap more than the limit.

BEP20: transfer amount exceeds balance

Fail with mistake 'BEP20: transfer corporeality exceeds balance'

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

If non, y'all may be trying to ship tokens that yous don't have in your wallet (for example, trying to send a token that is already assigned to a pending transaction). In this case, but make certain y'all have the tokens you're trying to use.

Firstly, let the team know which pool you're trying to unstake from, so they can acme up the rewards. If y'all're in a bustle to unstake and y'all don't mind losing your awaiting yield, effort an emergencyWithdraw:

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

1 .

Notice the contract address of the Syrup Puddle you're trying to unstake from. You can find it in your wallet's transaction log.
4 .

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

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

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

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

This error tends to announced when you're trying to unstake from an erstwhile 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 fail.

Issues with Prediction

Other bug

Provider Fault

Provider Fault No provider was found

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

Unsupported Concatenation ID

Switch your concatenation to BNB Smart Concatenation. Bank check your wallet's documentation for a guide if you demand assist.

Already processing eth_requestAccounts. Please wait.

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

Problems ownership SAFEMOON and similar tokens

To trade SAFEMOON, y'all must click on the settings icon and set 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
v% fee = used to add liquidity

This is also why you might not receive every bit much of the token equally you expect when you buy. Read more on How to Purchase Safe 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. Try using an alternative wallet.

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

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

Error: [ethjs-query]

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

Increase the gas limit for the transaction in your wallet. Cheque your wallet'due south documentation to learn how to increment gas limit.

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

Crusade unclear. Try these steps before trying over again:

Issues with Profile

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

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

Clear the cache and retry.
Retry on dissimilar 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.

ane .

You lot accept 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 nosotros tin can do nix.

1 .

Accept but 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-blazon username, then please wait for seconds.
three .

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

tindaltheresobted.blogspot.com

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

Tindal Theresobted