Troubleshooting & Support
What to check first and what to send when you need help.
Start with the exact error shown in the task row, toast, or dialog. Check the most likely dependency for that operation—wallet funds, RPC health, proxy health, account authentication, API keys, captcha balance, and your internet connection—then retry only the failed operation.
Collect Logs#
Open Settings → App → Show Logs. Zyper opens the correct log folder for Windows or macOS. Reproduce the problem once if it is safe to do so, then note the approximate local time so support can find the relevant entries.
Depending on the failure, the useful files may include zyper.log,
tasks.log, or funds-sessions.log. Keep the original files intact rather than
copying only the last visible line; the cause often appears earlier.
What to Send#
Send the relevant log files together with:
- why you are contacting support and what you were trying to do;
- the exact on-screen error and approximate time it happened;
- your Zyper version and operating system;
- the affected page, task/module name, chain, and public transaction hash or wallet address when relevant;
- the steps needed to reproduce the issue.
Never send a seed phrase, private key, wallet export, license key, API key, account token, proxy password, or backup password. Review screenshots for sensitive fields before attaching them.
Contact Support#
Send the report directly to Zyper support. You may also open a ticket in the official Zyper Discord if you prefer a tracked support conversation. Include a short reason in the first message—for example, “OpenSea task remains on Preparing” or “macOS update fails after download”—instead of sending an unexplained log file.