Troubleshooting

Common issues and how to resolve them.

Common Issues

Port Already in Use

Another process is using the port you're trying to start your server on.

Solution: Check what's using the port with `lsof -i :3000` and either stop the other process or configure your project to use a different port.

Server Won't Start

Your server fails to start or crashes immediately.

Solution: Check the output panel for error messages. Common causes include: missing dependencies, syntax errors, or invalid configuration files.

Dependencies Won't Install

Node package installation fails or hangs.

Solution: Try these steps: 1) Check your internet connection, 2) Clear npm cache with `npm cache clean --force`, 3) Delete node_modules and package-lock.json, 4) Try installing again.

Framework Not Detected

Nodev doesn't recognize your project's framework.

Solution: You can manually set the framework in project settings. This is useful for custom frameworks or when auto-detection fails.

Custom Domain Not Working

Your .nodev domain doesn't resolve or returns errors.

Solution: Make sure the domain is properly configured in project settings. Try restarting Nodev. Check that the server is actually running on the expected port.

Permission Denied

Nodev shows permission errors when trying to start servers.

Solution: Ensure Nodev has the necessary permissions. Check macOS Security & Privacy settings and grant Full Disk Access if prompted.

Getting Help

If you're still having trouble:

• Check the release notes for known issues

• Review documentation for your specific use case

• Contact support through the website

When reporting issues, please include: macOS version, Node version, steps to reproduce, and any error messages from the output panel.