All port conflict errors are now handled automatically. The system will work perfectly after every reboot.
Run this once:
Double-click: SETUP_AUTO_START.bat
That's it! After this one-time setup:
- Controller starts automatically when you log in
- Port conflicts are resolved automatically
- No manual intervention needed
Double-click: start.bat
Or in PowerShell:
.\run.ps1- ✓ Checks for port conflicts
- ✓ Stops any conflicting processes
- ✓ Starts cleanly on port 5010
- ✓ Opens dashboard at http://127.0.0.1:5010
- ✓ Windows loads
- ✓ You log in
- ✓ Controller starts automatically
- ✓ Port conflicts resolved
- ✓ Dashboard ready to use
All startup scripts now handle port conflicts:
run.ps1- Manual PowerShell startupstart.bat- Manual batch startuptools/auto_start_controller.ps1- Boot startuptools/auto_start_and_launch_all.ps1- Full automationtools/setup_auto_start.ps1- Auto-start configuration
.\run.ps1You should see:
- "Checking for processes using port 5010..."
- Either "Port 5010 is available" or "Process stopped"
- Application starts successfully
- Start the controller once
- Start it again in a new window
- Second instance automatically stops the first
- Second instance starts cleanly
SETUP_AUTO_START.batstart.batGet-ScheduledTask -TaskName "Local Nexus Controller"cd tools
.\disable_auto_start.ps1Once running, access at:
- URL: http://127.0.0.1:5010
- Services: Manage your registered services
- Ports: View port allocations
- Auto-discovery: Detect local services
These errors are now handled automatically:
- ✓ Port already in use
- ✓ Multiple instances running
- ✓ Stale processes from previous sessions
- ✓ Reboot conflicts
Everything is configured. The system is ready for reboot.
If you want auto-start, run SETUP_AUTO_START.bat once.
Otherwise, just use start.bat whenever you need the controller.