Troubleshooting

Varity Team Core Contributors Updated May 2026

Solutions to common issues when building with Varity.

Installation Issues

”command not found: varitykit”

The CLI is not installed or is not in your PATH.

Install the CLI:
Terminal window
```
pipx install varitykit
```
Verify installation:
Terminal window
```
varitykit --version
```
If still not found, check your Python path:
Terminal window
```
python -m varitykit --version
```

“ModuleNotFoundError: No module named ‘varitykit’”

Python dependencies are missing.

pip install --upgrade varitykit

Package installation fails

If npm package installation fails:

# Clear npm cache
npm cache clean --force

# Delete node_modules and reinstall
rm -rf node_modules package-lock.json
npm install

Deployment Issues

”Credentials not found”

Credentials are managed automatically by Varity. Run varitykit doctor to verify your setup. See Managed Credentials.

”Build failed”

Verify your build works locally:
Terminal window
```
npm run build
```
Check for TypeScript errors:
Terminal window
```
npx tsc --noEmit
```
Ensure all dependencies are installed:
Terminal window
```
npm install
```

“Upload failed”

Possible causes and solutions:

Cause	Solution
Network timeout	Try again - temporary network issue
Large files	Split into smaller chunks
Rate limiting	Wait a few minutes and retry
Credentials issue	Run `varitykit doctor` to verify

Authentication Issues

Varity deploys your app as-is and does not manage authentication. Sign-in is handled by whatever auth library or provider your app uses, so debug it the same way you would locally:

Confirm the deploy finished successfully:
Terminal window
```
varitykit app status
```
Check the browser console for errors on your live URL
Confirm any secrets your auth provider needs (API keys, client IDs, callback URLs) are set as environment variables. See Environment Variables.

”Domain not allowed” error

Your domain needs to be allowed for authentication. Contact support@varity.so to allow your domain, or include localhost for local development.

Session not persisting

Check that:

You’re not accidentally clearing localStorage
Cookies are enabled in the browser

Build Issues

Dependencies missing after install

Check package.json includes all of your app’s dependencies
Clear and reinstall:
Terminal window
```
rm -rf node_modules
npm install
```

Runtime Issues

”Network request failed”

Check network connectivity:

varitykit doctor

This will verify your connection to Varity’s infrastructure.

”Operation failed”

Common causes:

Error	Solution
Service not found	Verify configuration is correct
Invalid parameters	Check function arguments

Slow performance

Enable production mode:
Terminal window
```
npm run build && npm start
```
Check bundle size:
Terminal window
```
npm run analyze
```

CLI Issues

”varitykit doctor” shows failures

Run the doctor command to diagnose:

varitykit doctor

Common failures and fixes:

Check	Fix
Environment variables	Create `.env` file with required vars
Network connectivity	Check internet connection
Project structure	Ensure `package.json` exists
Dependencies	Run `npm install`

Deployment history not showing

Deployments are stored locally. Check:

ls ~/.varitykit/deployments/

If empty, no deployments have been made from this machine.

Getting More Help

If you’re still stuck:

Search existing issues: Varity on GitHub
Ask the community: Discord
Open a new issue with:
- Error message (full stack trace)
- Steps to reproduce
- varitykit doctor output
- OS and Node.js version
Email support: support@varity.so