If I Lost an Expired Permit Can I Order It Again

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

Issues on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

The transaction cannot succeed due to error: 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 as well depression or liquidity is too low.

ane .

Refresh your folio and try once more later.
2 .

Try trading a smaller amount at ane fourth dimension.
3 .
Increase your slippage tolerance:
1. 1 .
  
  Tap the settings icon on the liquidity page.
2. 2 .
  
  Increase your slippage tolerance a little and try once more.
4 .

Lastly, try inputting an amount with fewer decimal places.

This usually happens when trading tokens with low liquidity.

That means there isn't enough of one of the tokens yous're trying to swap in the Liquidity Pool: information technology's probably a pocket-size-cap token that few people are trading.

However, there's also the chance that you're trying to merchandise a scam token which cannot exist sold. In this case, PancakeSwap isn't able to block a token or render funds.

INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

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

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

Refresh your page and effort again, or try again later.

ane .

Tap the settings icon on the liquidity page.
2 .

Increase your slippage tolerance a picayune and try once more.

The error is acquired past 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).

Information technology might be the example that prices are updating likewise fast when and your slippage tolerance is too low.

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

In that location currently isn't a uncomplicated fashion to solve this effect from the PancakeSwap website: you'll demand to interact with the contract directly. You can add liquidity straight via the Router contract, while setting amountAMin to a small corporeality, and then withdrawing all liquidity.

Approve the LP contract

1 .

Select Write Contract , then Connect to Web3 and connect your wallet.
two .
In section "1. corroborate", corroborate the LP token for the router past inbound
1. 1 .
  
  spender (accost): enter the contract accost of the LP token you'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's exported. It shows your rest within the LP in the uint256 format, which yous'll need in the adjacent stride.

Add together or Remove Liquidity

ane .

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

Discover addLiquidity or removeLiquidity (whichever one yous're trying to practice)
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 depression amountAMin or amountBMin : endeavor one for both.
vi .

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

Deadline must be an epoch time greater than the fourth dimension 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 issue with ane of the tokens you are swapping.

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

This happened because you started making a transaction, merely you didn't sign and broadcast it until information technology was past the deadline. That means y'all didn't striking "Ostend" apace enough.

Pancake: K

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

Effort modifying the amount on "To" field. Therefore putting "(estimated)" symbol on "From". So initiate the bandy immediately.

This ordinarily 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.

Make sure you take 30% more tokens in your wallet than you intend to trade, or try to trade a lower amount. If you want to sell the maximum possible, endeavour 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 result is the malicious token issuer just suspended the trading for their token. Or they fabricated selling activity only possible for selected wallet addresses. Please ever exercise your own enquiry to avoid any potential fraud. If the token you are trying to swap but failed with this error code is coming from an airdrop, that is most likely a scam. Please do not perform whatever token approval or follow any links, your fund may be at risk if you try to exercise and then.

Transaction cannot succeed

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

Price Bear on too Loftier

Effort 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 fail. Please contact back up

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

Delight select "Receive WBNB" and retry.

If you got this mistake while trying to bandy:

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

This effect (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 exist due to their tokenomics, in which each purchase sends a % of the token to LPs.

The projects affected will likely non piece of work with the V2 router: they volition virtually likely need to create new versions of their tokens pointing to our new router address, and migrate whatsoever 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 error has been reported on mobile devices using Trust Wallet.

i .

Attempt the transaction over again with increased slippage allowance.
2 .

If i. does non resolve your problem, consider using another wallet such every bit 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 beingness 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 mistake message is displayed. This error has been reported across platforms.

1 .

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

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

This error happens when trading tokens with bereft allowance, or when a wallet has bereft funds. If you'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 .

Issues with Syrup Pools

BEP20: burn down amount exceeds balance

Fail with error 'BEP20: burn amount exceeds balance'

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

Go at least equally much SYRUP as the corporeality of CAKE that you're trying to unstake.

1 .

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

If that yet fails, y'all can perform an "emergencyWithdraw" from the contract direct to unstake your staked tokens.

2 .

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

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

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

This volition lose any yield that you lot haven't harvested all the same.

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

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

Out of Gas error

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

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

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

A limit of 200000 is usually enough.

The higher up example is from Metamask; check your wallet'southward 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 do.

Your wallet estimates that the gas limit is as well depression, and then the function call runs out of gas before the office call is finished.

BEP20: transfer corporeality exceeds allowance

Neglect with error 'BEP20: transfer amount exceeds assart'

one .

Utilize Unrekt.net to revoke approval for the smart contract you're trying to collaborate with
2 .

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

Try interacting with the contract once again.

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

BEP20: transfer amount exceeds balance

Fail with error 'BEP20: transfer corporeality exceeds remainder'

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

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

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

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

1 .

Find the contract accost of the Syrup Pool y'all're trying to unstake from. You tin find information technology in your wallet's transaction log.
4 .

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

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

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

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

This error tends to appear when y'all'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.

Bug with Prediction

Other issues

Provider Error

Provider Error No provider was institute

This happens when you 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'due south documentation for a guide if you lot need help.

Already processing eth_requestAccounts. Please wait.

Make certain you are signed in to your wallet app and it'south continued to BNB Smart Chain.

Problems buying SAFEMOON and similar tokens

To merchandise SAFEMOON, you must click on the settings icon and ready your slippage tolerance to 12% or more. This is considering 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 might not receive as much of the token as y'all look when you purchase. Read more than on How to Buy Safe Moon .

Internal JSON-RPC errors

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

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

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

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

Error: [ethjs-query]

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

Increase the gas limit for the transaction in your wallet. Cheque your wallet'south 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 request error"}}}'

Crusade unclear. Try these steps before trying over again:

Issues with Contour

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

We're investigating the logic backside this issue. Meanwhile please try the workaround.

Clear the cache 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 accept multiple wallets installed on the browser.

Root cause: Yous have multiple wallets installed on the browser. It may make a disharmonize between wallets. This is out of PancakeSwap's control and we can do nothing.

1 .

Accept but single wallet installed on browser, remove the others.
2 .

Reconnect the wallet and retry setting username over again.

Root cause: Network is unstable.

one .

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

Re-type username, then delight wait for seconds.
three .

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

grubbbrimmould.blogspot.com

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