Connection and transaction help
Find the cause of a problem without putting keys or funds at risk.
Browse all 38 guides
Ledger does not connect
Use a full HTTPS site tab in a supported desktop browser. Embedded pages can have additional USB restrictions.
Check the data cable, device unlock state, and that the XRP app is open.
Close Ledger Live and other browser tabs holding the device connection.
Try the alternate USB connection option, then reconnect the device if necessary.
If signing a particular transaction fails, check whether the installed XRP app supports it. Do not assume that a successful address connection proves every transaction type is supported.
CROSSMARK was not detected
Confirm the extension is installed and enabled in this browser profile. Check that it may run on the site, then refresh XRPFrontend and try connecting again. Refreshing discards any temporary test wallet in that tab, so finish or record your Testnet work first.
An account does not load
Verify the selected network and the full classic address. The same address can have different state on Testnet and Mainnet. “Not activated” on Testnet does not mean a Mainnet account is empty.
If the error mentions a connection, timeout, or server, check internet access and retry later. XRPFrontend relies on public XRPL endpoints. The Testnet faucet can fail separately from normal account queries.
A transaction fails
| Message or symptom | What to check |
|---|---|
| Insufficient spendable XRP | Leave room for reserve, object creation where applicable, and the fee. |
| Destination tag required | Obtain the recipient’s correct tag; never guess one. |
| Review expired | Prepare a fresh review; the unsigned one was older than two minutes. |
| Wallet changed the reviewed transaction | Reconnect and inspect the wallet response. XRPFrontend blocks altered fields. |
| tecNO_PERMISSION on CheckCash | Connect the account named as the check recipient. |
| Escrow will not finish or cancel | Check owner, original sequence, ledger time, condition, and expiration. |
| Check not found or expired | Verify the network and ID, then inspect whether it was cashed, cancelled, or expired. |
| Timeout after signing | Check the transaction hash and ledger state before resubmitting. |
What to include in a bug report
Record the operation, selected network, exact error text, browser, wallet type, and device/XRP app version when relevant. A transaction hash can help diagnose a public ledger result, but sharing it may expose account activity.
Remove sensitive personal information from screenshots. Never include recovery words, wallet seeds, private keys, or an unpublished escrow fulfillment. XRPFrontend currently has no in-app support inbox; contact admin@xrpfrontend.com with the error and public transaction hash if relevant.
Token or NFT data does not load
Read the provider cooldown message and wait until the displayed time before refreshing manually. Changing tabs, routes or wallet accounts does not lift the cooldown. A waiting request can retry once after a cooldown of up to one minute. The site does not serve persistent market snapshots.
If a request fails for another reason, refresh once after checking your connection. Artwork depends on external publishers and may remain unavailable even when ledger ownership is readable. Never sign or repeat a payment merely to fix missing market information.