Networking Issues

Solution:

1. Check that milmil is listening on 0.0.0.0, not 127.0.0.1 (localhost only)
2. Check firewall rules — ports 3000 (web) and 8080 (API) must be open
3. Try accessing via IP address (e.g. http://192.168.1.100:3000)
4. In Docker, ensure ports are mapped with -p 3000:3000 -p 8080:8080

Common causes:

1. milmil services not running — check with docker ps
2. Wrong upstream port in proxy config
3. Proxy trying HTTPS to upstream when milmil only serves HTTP

Solution: Verify services are running, then check proxy error logs (/var/log/nginx/error.log for Nginx).

Symptoms: Danmaku not loading, notifications not updating in real-time.

Solution:

1. Ensure your reverse proxy passes WebSocket upgrade headers — see Reverse Proxy
2. Check that both /ws and /api/ paths have WebSocket support configured
3. Some CDNs (Cloudflare free tier) have WebSocket limitations — check your CDN settings

Cause: The API and frontend are on different domains or ports without proper CORS headers.

Solution:

1. Use a reverse proxy to serve both frontend and API under the same domain (recommended)
2. If running separately, milmil's API sets CORS headers automatically based on the CORS_ORIGIN environment variable

Solution:

1. Check that port 42069 (or your configured TORRENT_LISTEN_PORT) is open and port-forwarded on your router
2. DHT needs time to bootstrap on first run — wait a few minutes
3. Check if your ISP blocks BitTorrent traffic
4. In Docker, the torrent port must be mapped: -p 42069:42069/tcp -p 42069:42069/udp