Troubleshooting
If something’s wrong, start with the logs:
<folder-with-zyper-aio.exe>\logs\zyper.log<folder-with-zyper-aio.exe>\logs\funds-sessions.logzyper.log rotates at 4 MiB to zyper.log.1. Grep for error, fail, or
the package prefix (e.g. tasks:, rpc:, nft:).
App won’t start
”Nothing happens when I double-click zyper-aio.exe”
Most likely:
- Defender quarantined it. Check Windows Security → Protection history.
- The
.exeis on OneDrive / a network drive. Move to plain local disk. - Another instance is already running. The Win32 single-instance gate silently exits second launches. Check Task Manager.
”License Gate stays up forever”
- Confirm internet — the gate hits
license.zyper.app. - Confirm your firewall isn’t blocking outbound HTTPS to that host.
- If you’ve moved machines, the HWID binding from a previous PC will fail. Visit license.zyper.app and click Reset machine.
Tasks won’t fire
”Status sits at Pending forever”
- No RPC for the chain. Add at least one on the RPC page.
- All RPCs unhealthy. Re-probe; check that endpoints answer
eth_chainIdcorrectly. The chip will be red if the chain ID doesn’t match the group.
”Every tx reverts”
- Wallet has no gas. Check balance on Wallets page.
- Wrong chain. Confirm the task group’s chain matches where the contract is.
- Contract isn’t open yet. Try Simulate mode for time-gated mints.
”Spam mode runs like Instant”
That’s expected — Spam parallel-nonce fanout is not yet wired. See Simulate / Spam / Instant.
Social tasks failing
”Cloudflare challenge page in the log”
The module is using the http engine on a CF-WAF-protected site. The fix is
on the module’s side (switch to the browser engine with in-page fetch),
not yours. Report it in Discord with the module name.
”captcha_unsolvable from solver”
The sitekey baked into the module no longer matches what the site serves. Sites rotate keys; the module needs an update.
”Account login expired”
The Discord / Gmail / X token has been invalidated. Re-test from the Accounts page. If the chip is red, replace the token (get a fresh one from the burner’s browser session).
”Captcha taking 60+ seconds”
Normal for Turnstile. Budget 90s/iteration in your head. Failures past 90s are real failures, not just slow runs.
NFTs
”Inventory shows 0 but I know the wallet holds tokens”
- The contract isn’t ERC-721 (might be ERC-1155 — not supported yet).
- The wallet was acquired the token recently and the deploy-block cache is
stale. Delete
nft_deploy_cache.txtunder your data dir and re-enumerate. - The contract is non-standard (no enumerable, no
tokensOfOwner, and the Transfer log scan failed for some reason). Check the log fornft:errors.
”Metadata images don’t load”
Token metadata cache (nft_metadata_cache.txt) is stored once per token ID.
If the contract uses tokenURI with mutable IPFS gateways and the gateway
changed, the cached URL may 404. Delete the cache file to refetch.
PnL
”PnL card is blank / says no data”
You haven’t set an Alchemy URL for the chain. Settings → PnL.
”Numbers look way off”
PnL counts ETH + WETH inflows. Sales paid in stablecoins or other tokens aren’t counted. If you’re getting paid in USDC, that’s expected today.
Updates
”Updater says signature failed”
Don’t ignore this. Report it in Discord — it means either:
- The release was tampered with in the bucket (unlikely), or
- A bug crept into the manifest signing flow (possible during a release).
The desktop refuses to apply, so you’re safe to stay on your current build.
When to ask for help
- Crashes that produce no log line at all — include screenshot of the error
dialog plus the last 100 lines of
zyper.log. - Reproducible task failures — include the task’s live-log modal output.
- Anything involving sensitive data (wallet keys, license keys, RPC URLs with API keys baked in) — never paste these in Discord. Redact before sharing.