Server Settings

Treat Server Settings as infrastructure and maintenance.

1. Web Server Port and Admin Port

Web Server Port

• Port used by the public radar (/AircraftList.json, map frontend).

Admin Port

• Port used by the admin panel (/admin).
• Recommended: use a dedicated admin port, separate from radar.

If AdminPort = 0 or equals WebServerPort, admin endpoints share the same port as public radar, which increases exposure.

2. Network Binding

This setting controls whether the server listens on:

1. localhost only,
2. all interfaces (0.0.0.0) for LAN/VPN/public routing.

A restart is required after changing binding behavior.

3. Radar Visibility

This setting controls radar authentication:

1. Public - radar is accessible without login.
2. Private - radar requires authentication.

This is independent from Network Binding.

4. Database and Imports

Database File Name

• SQLite database file path/name.
• Changing it may require restart.

Data import options

• OpenSky CSV
• ADS-B Exchange JSON/NDJSON
• Airport CSV (OurAirports-compatible)

Recommended process:

1. Confirm source URL is valid and in expected format.
2. Run import.
3. Check server logs.
4. Verify results on map/list.

5. Configuration Backup

This section provides:

1. settings export,
2. settings import.

After importing configuration:

1. verify ports,
2. verify binding,
3. restart service if required.

6. Danger Zone

Clear Application Data removes critical data (configuration, users, mappings, database).

Use only when:

1. performing full instance reset,
2. current backups exist,
3. irreversible data loss is accepted.