Reference · Troubleshooting
Troubleshooting
Common issues and how to fix them, grouped by area. Each row gives the symptom, the likely cause, and the fix. If you cannot find your issue, ask in the community on Telegram.
Most problems fall into four buckets: signing in, funding wallets, sending trades, and the app itself. Every fix follows the same path: read the symptom, find the cause, apply the fix.
Login and connection
| Symptom | Cause | Fix |
|---|---|---|
| Could not reach server on login | The terminal cannot reach its backend, usually the server or its database being down after a restart, not your connection. | Wait a moment and retry. If it persists, the backend is being brought back up: check the status channel on Telegram. Your funds and keys are unaffected by a login outage. |
| Logged out unexpectedly | Your session expired, or a fund-moving request was sent without a valid session token and was rejected as a safety measure. | Sign in again. Sessions are short by design so a stale tab cannot move funds. If it repeats, clear the site's stored data and log in fresh. |
Wallets and funding
| Symptom | Cause | Fix |
|---|---|---|
| Wallet not funded, or insufficient balance | The deposit has not confirmed yet, or it landed in a different role wallet than the one the action spends from. | Check the Wallets screen and confirm which wallet holds the balance. Fund the fund wallet for launches. If a deposit is pending, give it a few blocks, then refresh. |
| Bridged funds not showing up | The bridge has not reached finality, or you are looking at the wrong chain's balance. | Robinhood Chain settles in about a minute; a private Monero route takes 15 to 30 minutes. Wait for finality, then check both the Launch and Wallets screens, which show balances on both chains. |
Trades and launches
| Symptom | Cause | Fix |
|---|---|---|
| Transaction failed | The network dropped the transaction under load, slippage moved past your cap, or the priority fee was too low to land in time. | Retry. If it keeps failing, raise the priority fee and Jito tip in Settings so it lands during congestion, and widen slippage a little on volatile tokens. |
| Slippage exceeded | Price moved further than your slippage cap between quote and execution, common on thin or fast-moving pools. | Increase the max slippage on the trade, the 0.5%, 1%, and 3% presets or a higher custom value on very volatile tokens, then resend. A wider cap fills more often but at a worse worst case price. |
| Token not graduating | It has not reached the launchpad's graduation threshold of buys, or momentum stalled after launch. | Graduation is driven by volume on the curve. Keep buys and attention flowing, use bump tooling to sustain activity, and check the launchpad's own threshold. This is market driven, not a bug. |
RPC and the app
| Symptom | Cause | Fix |
|---|---|---|
| RPC errors or slow quotes | The Solana RPC endpoint is degraded or rate limiting requests during heavy network load. | Wait and retry; transient RPC issues clear on their own. If quotes stay stale, reload the screen to reconnect the feed. Persistent outages are posted to the status channel. |
| Video not playing | The browser blocked autoplay, the tab is throttled in the background, or a strict content or data setting is on. | Interact with the page once, keep the tab in the foreground, and disable any aggressive data saver or content blocker for the site. It is cosmetic and does not affect trading. |
| Mobile layout looks off | A cached older stylesheet, or the page opened before it finished loading. | Pull to refresh, or hard reload. Open the navigation with the menu button at the top left. Wide tables scroll sideways on their own, so a refresh usually settles it. |
When in doubt, retry then refresh
A large share of transient issues, dropped transactions, stale quotes, and RPC hiccups clear on a retry or a reload. If a problem survives both, bring it to the Telegram community with the exact message you saw.