Troubleshooting
Record the network, page URL, vault and account addresses, intended action, and exact error before changing settings or retrying. Never share a seed phrase, private key, password, or signing secret.
Common errors
E_AccountLiquidity
Meaning: The requested action would leave the account above the permitted borrow LTV or otherwise fail its account-status check. A position can remain below its liquidation LTV and still be unable to take a risk-increasing action.
Action: Reduce the borrow or withdrawal, add eligible collateral, or repay debt. Review the controller vault, enabled collateral, current oracle values, borrow LTV, and liquidation LTV before retrying.
E_InsufficientCash
Meaning: The vault does not have enough available underlying liquidity for the requested withdrawal or borrow. This can also affect collateral-to-repay flows when the source vault lacks liquidity.
Action: Reduce the amount or wait for liquidity to return. Check the target vault's available liquidity before resubmitting.
E_RepayTooMuch
Meaning: The requested repayment exceeds the current debt amount after interest and rounding.
Action: Use Max when available or submit an amount below the displayed total debt.
E_SupplyCapExceeded or E_BorrowCapExceeded
Meaning: The requested action would exceed the relevant vault cap.
Action: Reduce the amount or wait for capped supply or capped borrows, respectively, to fall. A curator may be able to change a cap only if the deployed roles authorize it.
Multiple wallet extensions active
Multiple extensions can compete for the wallet-provider connection and signing request. Disable extensions you are not using, refresh the page, reconnect the intended wallet, and retry.
RPC issues
An unavailable or stale RPC can prevent simulation, reads, or transaction submission. Switch to another RPC you trust, confirm the wallet is on the intended network, and check whether a transaction hash was produced before retrying.
Gasless signatures unsupported
Some wallets handle the typed-data signatures used for gasless (Permit2) approvals poorly. If signature prompts fail or approvals stall, open Settings using the gear button in the top-right corner and disable Gasless signatures to fall back to standard approval transactions, then retry the flow.
Basic checks
- Reconnect the wallet and confirm the account and network.
- Refresh the page after disabling conflicting extensions or changing RPC.
- Inspect the wallet error and browser console; remove secrets before sharing logs.
- If a transaction hash exists, inspect its status and revert data on the relevant explorer.
- Recheck vault liquidity, caps, oracle state, account health, and approvals because state may have changed.
Reporting an issue
Report issues and get user support in the Euler community Discord. If the issue is security related, report it through the bug bounty instead — never disclose a potential vulnerability publicly.
Include:
- action, page URL, and approximate time;
- network, public account or sub-account, and vault address;
- transaction hash, simulation result, and exact error;
- wallet, browser, device, and versions;
- redacted screenshots; and
- relevant console or network errors with API keys, authorization headers, cookies, RPC credentials, and personal information removed.