Appearance
Troubleshooting
This guide covers common issues you might encounter while developing with Jubiloop and their solutions.
Common Issues
Husky Hook Issues
If git hooks aren't running when you commit:
bash
# Re-install Husky hooks
npm run prepare
# Ensure pre-commit hook is executable
chmod +x .husky/pre-commitIf you need to bypass hooks for a specific commit:
bash
git commit -m "Your message" --no-verifyPort Conflicts
Jubiloop uses several ports for different services. If you encounter port conflicts:
Default Ports
- Frontend (React): 3000
- Backend (AdonisJS): 3333
- Marketing (Next.js): 3001
- PostgreSQL: 5433
- Redis: 6379
- Caddy: 80, 443
Check What's Using Ports
bash
# Check specific ports
lsof -i :3000 # Frontend
lsof -i :3333 # Backend
lsof -i :3001 # Marketing
lsof -i :5433 # PostgreSQL
lsof -i :6379 # RedisSolutions
Stop conflicting services:
bash# Kill process using a port (replace PID with actual process ID) kill -9 <PID>Change port numbers in configuration files:
- Frontend:
apps/webapp/package.jsonorvite.config.js - Backend:
apps/server/.env - Marketing:
apps/marketing/package.json - Infrastructure:
infra/local_dev/docker-compose.yml
- Frontend:
Node Version Issues
Jubiloop requires Node.js v22 or later (LTS version).
bash
# Check current version
node --version
# Using nvm to switch versions
nvm install 22
nvm use 22
# Set default version
nvm alias default 22Turborepo Cache Issues
If you experience unexpected build behavior or stale outputs:
bash
# Clear Turborepo cache
npx turbo clean
# Force rebuild without cache
npx turbo build --forceDocker Container Issues
Database Connection Failures
bash
# Check if containers are running
cd infra/local_dev
docker compose ps
# Restart specific services
docker compose restart postgres redis
# View logs for errors
docker compose logs postgres
docker compose logs redis
docker compose logs caddyReset All Data (Warning: This will delete all local data)
bash
cd infra/local_dev
docker compose down -v
docker compose up -d
# Re-run migrations after reset
cd ../..
npm run migration:runApplication Not Accessible via HTTPS
If applications show connection errors when accessing via Caddy:
1. Ensure Apps Listen on All Interfaces
Your applications must listen on 0.0.0.0 (not just localhost):
Vite (React app): Check
vite.config.jshas:jsserver: { host: '0.0.0.0' }AdonisJS: Your
.envshould have:bashHOST=0.0.0.0
2. Verify Applications Are Running
bash
# Check if apps are actually running
lsof -i :3000 # Should show your React app
lsof -i :3333 # Should show AdonisJS
lsof -i :3001 # Should show Next.js3. Regenerate HTTPS Certificates
bash
cd infra/local_dev
./setup-https.sh
docker compose restart caddyBuild Failures
Missing Dependencies
bash
# Clean install all dependencies
rm -rf node_modules package-lock.json
rm -rf apps/*/node_modules packages/*/node_modules
npm installTypeScript Errors
bash
# Check TypeScript configuration
npx tsc --noEmit
# Build specific package to isolate issues
npx turbo build --filter=webappDatabase Migration Issues
Migration Fails
bash
# Check database connection
cd infra/local_dev
docker compose exec postgres psql -U postgres -c '\l'
# Reset migrations (Warning: Deletes all data)
cd apps/server
node ace migration:rollback --batch=0
node ace migration:runSeeding Fails
bash
# Run seeds with verbose output
cd apps/server
node ace db:seed --debugGetting Help
If you're still experiencing issues:
- Check logs for detailed error messages
- Search existing issues in the project repository
- Create a new issue with:
- Description of the problem
- Steps to reproduce
- Error messages/logs
- Your environment (OS, Node version, etc.)
Useful Commands Summary
bash
# Infrastructure
cd infra/local_dev
docker compose up -d # Start all services
docker compose logs -f # View all logs
docker compose restart <service> # Restart specific service
docker compose down -v # Stop and remove everything
# Development
npm run dev # Start all apps
npx turbo clean # Clear build cache
npm run test # Run all tests
npm run migration:run # Run database migrations
# Debugging
lsof -i :<port> # Check port usage
node --version # Check Node version
docker --version # Check Docker versionPrevious: Local Development Setup