Troubleshooting

Common Issues

"No valid entry point found (e.g., index.html)"

Your ZIP must contain an index.html file. Make sure you're zipping the contents of your build folder, not the folder itself:

# ✗ Wrong — zips the folder
zip -r site.zip dist/

# ✓ Correct — zips the contents
cd dist && zip -r ../site.zip .

NetLaunch searches up to 5 levels deep and checks common build directories (build/, dist/, web/, public/, out/), but putting index.html at the root is safest.


"Invalid API key"


"Cannot redeploy: no site name found"

This happens with older deployments. The site name is extracted from the deployment URL as a fallback. If neither works, deploy via CLI instead:

netlaunch deploy -s your-site-name -f ./new-build.zip

Deployment stuck in "Deploying" status

The deployment function has a 9-minute timeout. If it's been longer:


"command not found: netlaunch"

# Install globally
npm install -g netlaunch

# Or use npx
npx netlaunch deploy -s my-app -f ./dist.zip

Make sure Node.js 18+ is installed: node --version


Login opens browser but CLI doesn't detect it


Site shows old content after redeploy


Getting Help

FAQ

Q: Can I use a custom domain? A: Not yet — coming soon. Currently all sites are at .web.app.

Q: Can I deploy a backend/API? A: No. NetLaunch is for static sites only (HTML, CSS, JS, images, fonts).

Q: Is there a file size limit? A: 100 MB per ZIP upload.

Q: Can I delete a deployment? A: Yes — from the dashboard site details page.

Q: Do I need to login every time? A: No. netlaunch login stores credentials that auto-refresh. You only need to login once.

Q: Can multiple people deploy to the same site? A: Yes — anyone with a valid API key can deploy to any site name. Use the same site name to update an existing deployment.