Skip to main content

Network Ports

This document outlines all network ports used by the LHM application for various communication protocols and services.

Port Configuration​

Core Application Ports​

Port 1349 - Main Application Server​

  • Protocol: HTTP/HTTPS + WebSocket (Socket.IO)
  • Service: Primary backend API and real-time communication

Media Streaming Ports​

Port 1935 - RTMP Streaming Server​

  • Protocol: RTMP (Real-Time Messaging Protocol)
  • Service: Video streaming server
  • Status: Always active

Port 8000 - Media HTTP Server​

  • Protocol: HTTP
  • Service: Media server web interface
  • Status: Always active

Game Integration Ports​

Port 1350 - League of Legends API​

  • Protocol: HTTP
  • Service: LoL companion application interface
  • Status: Active when League of Legends is detected
  • Dependency: Requires League of Legends client to be running

Port 1386 - LHM Replays WebSocket Server​

  • Protocol: WebSocket
  • Service: LHM Replays communication
  • Status: Active when LHM Replays functionality is enabled

Network Security​

CORS Configuration​

The main server (port 1349) accepts connections from:

  • http://localhost:1349
  • http://{internal_ip}:1349
  • http://{public_ip}:1349

Firewall Considerations​

Ensure the following ports are accessible:

  • 1349: Required for main application functionality
  • 1935: Required for streaming capabilities
  • 8000: Required for media server access
  • 1350: Required for League of Legends integration
  • 1386: Required for LHM Replays functionality

Development Notes​

Port Scanning​

The application includes automatic port scanning functionality to:

  • Detect development servers on localhost
  • Monitor for game client availability
  • Handle port conflicts gracefully

Troubleshooting​

Common Port Conflicts​

  • Port 1349: Ensure no other applications are using this port
  • Port 1935: May conflict with other streaming software (OBS, etc.)

Connectivity Issues​

  1. Verify firewall settings allow traffic on required ports
  2. Ensure CORS origins match your network configuration
  3. Confirm no port binding conflicts with other applications