Cyberflix Unknown Error Please Try Again

Sometimes you lot may discover yourself facing a problem that doesn't have a clear solution. These troubleshooting tips may help you solve issues y'all run into.

Issues on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

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

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

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

1 .

Refresh your page and endeavor again after.
2 .

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

Lastly, try inputting an amount with fewer decimal places.

This ordinarily happens when trading tokens with low liquidity.

That means in that location isn't enough of one of the tokens you're trying to swap in the Liquidity Puddle: it's probably a small-cap token that few people are trading.

Withal, 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 block a token or return funds.

INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

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

You're trying to add/remove liquidity from a liquidity pool (LP), just at that place isn't enough of one of the two tokens in the pair.

Refresh your folio and endeavour again, or try again later.

i .

Tap the settings icon on the liquidity folio.
2 .

Increase your slippage tolerance a little and try once more.

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

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

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

There currently isn't a simple way to solve this event from the PancakeSwap website: you'll need to interact with the contract directly. You can add together liquidity directly via the Router contract, while setting amountAMin to a small corporeality, so withdrawing all liquidity.

Corroborate the LP contract

1 .

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

Query "balanceOf"

two .

In 5. balanceOf , input your wallet address and striking Query .
iii .

Proceed track of the number that'southward exported. It shows your rest within the LP in the uint256 format, which you'll need in the next pace.

Add or Remove Liquidity

1 .

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

Observe addLiquidity or removeLiquidity (whichever one y'all'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" to a higher place.
5 .

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

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

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

This tin can cause very loftier 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 effect with one of the tokens you are swapping.

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

This happened because yous started making a transaction, merely you didn't sign and circulate it until it was past the deadline. That means you lot didn't striking "Confirm" quickly plenty.

Pancake: G

The transaction cannot succeed due to error: Pancake: Yard. This is probably an consequence with one of the tokens you lot 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 bandy a token with its own fee.

Pancake: TRANSFER_FAILED

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

Make sure yous have thirty% more tokens in your wallet than you intend to merchandise, or endeavour to merchandise a lower amount. If you desire to sell the maximum possible, try 70% or 69% instead of 100%. Caused by the design of Restorative Rebase tokens like tDoge or tBTC. Understand how restorative rebase tokens piece of work .

Another possible cause of this upshot is the malicious token issuer but suspended the trading for their token. Or they made selling activeness simply possible for selected wallet addresses. Please always do your own research to avoid any potential fraud. If the token you are trying to swap but failed with this error lawmaking is coming from an airdrop, that is most likely a scam. Delight do not perform whatsoever token approving or follow whatsoever links, your fund may be at risk if you try to do so.

Transaction cannot succeed

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

Price Impact too High

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

estimateGas failed

This transaction would neglect. Please contact back up

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

Please select "Receive WBNB" and retry.

If you lot 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 past the projection team.

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

While this practise is ill-advised at best, the reason for these projects having done this appears to exist 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 most likely need 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 any projects which created such tokens should as well make efforts to prevent their users from adding them to V2 LP.

Cannot read property 'toHexString' of undefined

"Unknown error: "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 .

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 allowance on Trust Wallet.

The exact details of the trouble are still existence 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 error message is displayed. This fault has been reported across platforms.

1 .

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

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

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

Issues with Syrup Pools

BEP20: burn amount exceeds residue

Neglect with error 'BEP20: burn amount exceeds balance'

Y'all don't have enough SYRUP in your wallet to unstake from the CAKE-Block pool.

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

ane .

Buy SYRUP on the exchange. If you desire to unstake 100 CAKE, yous need at least 100 SYRUP.

If that nevertheless fails, you can perform an "emergencyWithdraw" from the contract directly 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 volition unstake your staked tokens and lose any uncollected CAKE yield.

This volition lose any yield that you haven't harvested nonetheless.

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

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

Out of Gas error

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

Yous take prepare 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 finish what it's trying to practise.

Your wallet estimates that the gas limit is too low, so the office call runs out of gas before the part call is finished.

BEP20: transfer amount exceeds assart

Neglect with error 'BEP20: transfer amount exceeds allowance'

i .

Use Unrekt.net to revoke approving for the smart contract y'all're trying to interact with
two .

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

Endeavor interacting with the contract again.

This happens when you set a limit on your spend allowance when y'all outset approved the contract, then try to bandy more than than the limit.

BEP20: transfer corporeality exceeds balance

Neglect with mistake 'BEP20: transfer amount exceeds balance'

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

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

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

Y'all can perform an "emergencyWithdraw" from the contract straight to unstake your staked tokens.

1 .

Find the contract address of the Syrup Pool you're trying to unstake from. You tin notice it in your wallet's 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 will lose any yield that you haven't harvested yet.

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

Issues with Prediction

Other issues

Provider Error

Provider Mistake No provider was found

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

Unsupported Chain ID

Switch your concatenation to BNB Smart Chain. Bank check your wallet's documentation for a guide if you need assistance.

Already processing eth_requestAccounts. Please wait.

Brand sure yous are signed in to your wallet app and information technology'southward connected to BNB Smart Concatenation.

Bug buying 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 x% fee on each transaction :

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

This is also why yous might not receive as much of the token as you expect when you purchase. Read more on How to Buy Safe Moon .

Internal JSON-RPC errors

"MetaMask - RPC Mistake: Internal JSON-RPC mistake. 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 culling wallet.

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

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

Error: [ethjs-query]

Error: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"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":{"lawmaking":-32603,"data":{"code":-32603,"message":"handle request error"}}}'

Cause unclear. Endeavour these steps before trying once again:

Issues with Profile

Oops! We couldn't find whatever Pancake Collectibles in your wallet.

Nosotros're investigating the logic behind this issue. Meanwhile please endeavour 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

At that place are two possible causes.

1 .

You have multiple wallets installed on the browser.

Root cause: Y'all accept multiple wallets installed on the browser. It may brand a disharmonize between wallets. This is out of PancakeSwap'south control and we tin can practice nothing.

1 .

Take 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.
3 .

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

wickhamwhines.blogspot.com

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

Wickham Whines