Server setup

Download the server

Download the current release ZIP from GitHub Releases. The package contains IL2-SR-Server.exe and the required server files.

Use a separate folder for each SRS server instance. A client installation is not required on the dedicated server unless that machine also needs to run the client.

Start an instance

Run the server executable normally, or supply a specific configuration file:

IL2-SR-Server.exe -cfg="C:\IL2-SRS\instances\combatbox-main.cfg"

Set a unique server port for each instance. Ensure the corresponding TCP and UDP traffic is allowed through Windows Firewall and any upstream router or hosting-provider firewall.

server.cfg

The server creates missing persistent settings in server.cfg during startup while preserving existing values. Use the server UI for normal changes, then retain the generated configuration with your instance backups.

Important settings include:

• server port
• coalition radio security
• spectator audio
• realistic TX behaviour
• second-radio availability
• channel limit
• optional channel names
• optional majority squad channel labels
• tuned/client count display
• optional collision effects
• optional Pilot Roster JSON path

Connected clients can inspect the capabilities currently advertised by the server:

Do not place credentials or private filesystem paths in release packages. RCon credentials and server-only roster paths are not synchronized to clients by current builds.

Channel names

Server owners can assign optional names that appear on updated clients. Select EDIT beside Channel Names in the server app, or add a dedicated section to server.cfg:

[Channel Names]
1=Command
2=Tower/ATC

Use one setting per channel. Channels that are omitted or left blank continue to appear as CHN 1, CHN 2, and so on. Channel names affect only the client display and spoken channel announcements; channel numbers and radio frequencies remain unchanged. Experimental CHANNEL_NAMES values from earlier beta builds are migrated automatically when the server starts.

Majority squad channel labels

Server owners can allow clients to append a squad tag to channel names above channel 2. Enable Squad Channel Labels in the server window, or set:

[General Settings]
SHOW_SQUAD_CHANNEL_LABELS=true

The feature is disabled by default. A tag is shown only when at least two friendly pilots are on the channel and one recognized squad holds a strict majority. Ties, solo pilots, and channels 1 and 2 retain their normal channel names.

Server theme

Use Server Theme in the server window to switch immediately between the persistent White and Dark themes. White is the default. The local preference is stored under [Server Settings] and is not sent to connected clients:

[Server Settings]
SERVER_UI_THEME=Dark

The Server Health header remains visible at the top of the main window. Its service state verifies both the TCP control listener and UDP voice listener, and can report STARTING, RUNNING, DEGRADED, or STOPPED. It also shows the listening port, server uptime, connected clients, established UDP voice links, recent transmitters, and process memory use. These values are calculated locally and do not add network traffic. Start/Stop Server and Client Admin remain available in the fixed footer.

Client administration

Select Client Admin to expand the live client table from the right side of the main server window. Search across pilot names, assigned callsigns, coalition, and radio channels, or filter the table by coalition. Click a column header to sort it; radio channels are sorted numerically. Active filters and sorting update as live radio and voice-link data changes. The table shows each client’s Radio 1 and Radio 2 channels, UDP voice-link state, and server-side mute state. Kick, ban, mute, and unmute actions remain available per client.

Client compatibility

Read each release’s compatibility notes before deploying experimental features. Updated clients can normally communicate with older Community Edition servers, but a server-controlled capability is available only when the server advertises or signals it.

Logs

The server writes serverlog.txt in its application directory. Include this log when reporting synchronization, configuration, roster-file, or voice-routing problems.

Pilot Roster

To provide assigned callsigns and aircraft names to connected clients, continue with Pilot Roster integration.