๐Ÿ”ง Troubleshooting Guide

โŒ Can't Connect to Server

Check if both services are running:

  • Signaling server should be running on port 3001
  • Next.js app should be running on port 3000
  • Run: npm run dev:full

๐Ÿ“ฑ Devices Not Appearing

  • Make sure all devices are on the same WiFi network
  • Check firewall settings - port 3001 needs to be accessible
  • Try refreshing the browser page
  • Ensure the signaling server is accessible: http://[HOST-IP]:3001

๐Ÿ“ File Transfer Fails

  • WebRTC connection may be blocked by network/firewall
  • Try with smaller files first (under 10MB)
  • Check if browser supports WebRTC (Chrome/Firefox recommended)
  • Ensure both devices accept the file transfer request

๐ŸŒ Network Configuration

For other devices to access the app:

  • Find your IP address: ifconfig (Mac/Linux) or ipconfig (Windows)
  • Access from other devices using: http://[YOUR-IP]:3000
  • Example: http://192.168.1.100:3000

๐ŸŒ Browser Compatibility

Recommended browsers:

  • โœ… Chrome/Chromium (best support)
  • โœ… Firefox
  • โœ… Edge
  • โš ๏ธ Safari (limited WebRTC support)

โš ๏ธ Common Errors

๐Ÿงช Quick Test

To test if everything is working:

  1. Open the app in two browser tabs
  2. Set different device names in each tab
  3. Try sending a small file between the tabs
  4. If this works, the issue is likely network-related