-
-
Notifications
You must be signed in to change notification settings - Fork 2
Troubleshooting
Common issues and their solutions.
Always run the diagnostic tool before reporting issues:
diagnose.bat # Windows
./diagnose.sh # Linux
Output: diagnostics_YYYYMMDD_HHMMSS.txt in the project root. This collects OS version, Python/Node/CUDA versions, nvidia-smi, installed packages, and recent logs. Attach this file to any GitHub issue.
'python' is not recognized as an internal or external command
- Windows: Reinstall Python with "Add to PATH" checked, or add manually via System Properties → Environment Variables
-
Linux:
sudo apt install python3.10 python3.10-venv python3-pip -
Verify:
python --version
torch.cuda.is_available() # returns False
- Check
nvidia-smi— if it fails, drivers aren't installed - Verify CUDA version ≥ 12.1 in
nvidia-smioutput - Check PyTorch CUDA:
python -c "import torch; print(torch.version.cuda)" - If PyTorch reports CPU-only, reinstall:
pip install torch torchvision --index-url https://download.pytorch.org/whl/cu121
npm ERR! ERESOLVE unable to resolve dependency tree
Clear cache and retry:
npm cache clean --force
npm install
- Do NOT install in
C:\,Program Files, OneDrive, Dropbox, or Google Drive - Install in a path you own:
C:\Users\YourName\Projects\
chmod +x install.sh start_services_local.sh restart.sh
# Windows — find and kill process on port 3000
netstat -ano | findstr :3000
taskkill /PID <pid> /F
# Linux — find and kill
lsof -ti:3000 | xargs kill -9
Or use a different port:
start_services_local.bat --port 4000 --backend-port 9000
-
nvidia-smi— verify GPU is detected -
nvidia-smi --query-gpu=memory.free,memory.total --format=csv— check VRAM - Check
logs/app_YYYYMMDD.logfor error details - Run the diagnostic tool
- Open a GitHub issue with the diagnostic output
Supervisor manages the services. Check status:
supervisorctl status
supervisorctl restart all
If you see node_modules/ in the project root (not in frontend/), it was created by a shadcn CLI command running in the wrong directory. It is safe to delete.
Logs should stream in real time. If they appear frozen:
- The log poller uses a
total_lines_writtencounter (not a fragiledeque-relative index) -
PYTHONUNBUFFERED=1and the-uflag ensure stdout streams - Try switching browser tabs and back — the visibility-aware poller should re-sync
NaN loss commonly occurs with:
-
CAME optimizer with
fp16— usebf16instead -
CAME with conservative preset — was
fp16+conv_dim: 32; fixed tobf16+conv_dim: 0 - Very short prompts — SDXL NaN loss root cause was a CLIP mask bug (fixed upstream)
When opening a GitHub Issue:
- Run the diagnostic tool and attach the output
- Include:
- Your OS and deployment mode (local/cloud)
- GPU model and VRAM
- Python and Node.js versions
- Error output / logs
- Steps to reproduce
- Training config (sanitized of personal paths)
Use when the install is in a broken state that reinstalling hasn't resolved:
python clean_slate.py --dry-run # Preview
python clean_slate.py # Remove build artifacts, .venv, node_modules
python clean_slate.py --nuclear # Also remove models, datasets, outputs
After running, re-run the installer.
- Search existing issues
- Ask in Discord