Troubleshooting Errors

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

Challenges Encountered on the Exchange

INSUFFICIENT_OUTPUT_AMOUNT

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

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

Solution

• Refresh your page and try again later.

• Try trading a smaller amount at one time.

• Increase your slippage tolerance:

  1. Tap the settings icon on the liquidity page.

  2. Increase your slippage tolerance a little and try again.

• Lastly, try inputting an amount with fewer decimal places

Reason

This usually happens when trading tokens with low liquidity.

That means there isn't enough 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's also the chance that you're trying to trade a scam token which cannot be sold. In this case, PacificSwap isn't able to block a token or return fund

INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT

Fail with error 'PacificRouter: INSUFFICIENT_A_AMOUNT' or Fail with error 'PacificRouter: INSUFFICIENT_B_AMOUNT'

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

Solution

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

Still doesn't work?

1. Tap the settings icon on the liquidity page.

2. Increase your slippage tolerance a little and try again.

Reason

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).

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

PacificRouter: EXPIRED

The transaction cannot succeed due to error: PacificRouter: EXPIRED. This is probably an issue with one of the tokens you are swapping.

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

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

Pasific: TRANSFER_FAILED

The transaction cannot succeed due to error: execution reverted: Pacific: TRANSFER_FAILED

Make sure you have 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, try 70% or 69% instead of 100%. Caused by the design of Restorative Rebase tokens like tDoge or tBTC.

Another possible cause of this issue is the malicious token issuer just suspended the trading for their token. Or they made selling action only 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 code is coming from an airdrop, that is most likely a scam. Please do not perform any token approval or follow any links, your fund may be at risk if you try to do so.

Transaction cannot succeed

Try trading a smaller amount, or increase slippage tolerance via the settings icon and try 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 try again. This is caused by low liquidity.

estimateGas failed

This transaction would fail. Please contact support

Solution

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

Please select "Receive WETH" and retry.

If you got this error while trying to swap:

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

Reason

This issue (while swapping) is caused by tokens which have hard-coded the V1 PacificSwap 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 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.

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

Solution

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.

Reason

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

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

Solution

1. Check to make sure you have sufficient funds available.

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

Reason

This error happens when trading tokens with insufficient allowance, 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 work first with this guide to Rebase tokens.

Out of Gas error

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

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

Solution

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 example is from Metamask; check your wallet's documentation if you aren't sure how to adjust the gas limit.

Reason

Basically, your wallet (Metamask, Trust Wallet, etc.) can't finish what it's trying to do.

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

ERC20: transfer amount exceeds allowance

Fail with error 'ERC20: transfer amount exceeds allowance'

Solution

1. Use Unrekt.net to revoke approval for the smart contract you're trying to interact with

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

3. Try interacting with the contract again

Reason

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

ERC20: transfer amount exceeds balance

Fail with error 'ERC20: transfer amount exceeds balance'

You're probably trying to unstake from a 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 send a token that is already assigned to a pending transaction). In this case, just make sure you have the tokens you're trying to use.

Solution

Firstly, let the team know which pool you're trying to unstake from, 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 directly to unstake your staked tokens.

1. Find the contract address of the Syrup Pool you're trying to unstake from. You can find it in your wallet's transaction log.

2. Go to https://pacific-explorer.manta.network and in the search bar, enter the contract address.
3. Select Write Contract.

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

Reason

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

Unsupported Chain ID

Switch your network to Mantle Network. Check your wallet's documentation for a guide if you need help.

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, "message": "insufficient funds for transfer" } - Please try again.

You don't have enough ETH to pay for the transaction fees. You need more ERC-20 network ETH 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's 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"}}}'

Cause unclear. Try these steps before trying again:

1. Increase gas limit

2. Increase slippage

3. Clear cache

Checking username keeps spinning

There are two possible causes.

1. You have multiple wallets installed on the browser.

2. Network issue.

Solution 1

Root cause: You have multiple wallets installed on the browser. It may make a conflict between wallets. This is out of PacificSwap 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.

Solution 2

Root cause: Network is unstable.

You have to retry.

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.