Reference

Troubleshooting

Most issues come down to a permission, a connection or a stale session. Start here.

On the confirmation page, click click here to open VIfix manually. If your browser asks whether to open VIfix, allow it.

Check your internet connection or VPN. If you signed in before, the app keeps working offline for up to 72 hours.

Scanning#

A file wasn't scanned: it may be gitignored, over 1 MB, minified or binary. See what is skipped.
“Plan limit reached”: you've used this period's scans. Wait for the reset or upgrade.

A repo is missing from the list: the token wasn't given access to it. Edit the token on GitHub and add the repo.
Pull request refused: the file changed on GitHub since your scan. Scan again, then regenerate the fix.
“Resource not accessible”: the token needs Contents and Pull requests set to Read and write.

SSL errors: VIfix verifies certificates by default. Use the connection string from your provider's dashboard, which includes the right SSL settings.
Permission denied during audit: grant the audit role read access, for example pg_read_all_data on Postgres.
Can't execute a fix: fixes need an owner account. Use Save as migration instead.

“Can't reach the VIfix desktop app”: open VIfix and make sure the server is switched on under MCP Server.
“Outside the allowed folders”: add the project folder on the MCP Server page.
After changing a client's config file, fully quit and reopen the client.

Email hello@getvifix.com and include your app version from Settings → About. Check the FAQ too.