Troubleshooting Vooki Pro

Troubleshooting Vooki Pro

A page does not load fully in the recording window

  • Check that the site loads in your normal browser from the same machine and network (VPN, allow-lists).
  • If the scan traffic must go through a corporate proxy, set it under Settings. Vooki Pro supports HTTP and SOCKS proxies for outbound traffic.
  • If the traffic was captured elsewhere, import it with Recordings → Import HAR instead.

The scan finished with very few findings or URLs

  • Open the scan's Overview and check URLs discovered in scope. If it is a handful on a large app, fix discovery before trusting the result.
  • Single-page app? Use Hybrid discovery with a recording, and keep Discover background / API requests ticked.
  • Check Logs for WAF or CDN blocking. Lower the speed (Stealth), or ask to allow-list the scanning machine on staging.

Nothing was found behind the login

  • The session probably expired, or the scanner logged itself out. Add */logout to Discovery exclude and Attack exclude.
  • Enable Auto re-login if session expires during scan.
  • Check token lifetimes. A one-hour token on a four-hour scan leaves most of the scan unauthenticated. Use OAuth2 client credentials where you can.

Activation fails

  • Check that the machine can reach the internet and that the key was entered exactly as issued.
  • Installs are unlimited, so a key active on another machine is never the cause. Check whether the subscription has expired.

The app closed unexpectedly or ran out of memory

  • The full error is in ~/.vooki-pro/logs/crash.log. Send it to support.
  • The AI model uses about 5 GB of RAM during a scan, and 16 GB is the minimum for the machine. Close other heavy apps and make sure no earlier Vooki Pro instance is still running.

Still stuck?

Email support@vookify.com with the version from Settings → About, your operating system and the crash log if there is one. You can also ask in the community forum.