04. Server Settings
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:
- localhost only,
- 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:
Public- radar is accessible without login.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)
- BaseStation SQLite upload (
BaseStation.sqb,.sqlite,.db,.sqlite3)
BaseStation file import note:
- Use the file selector in Server Settings (no manual path typing required).
Replace- swaps the whole DB file and creates a.bakbackup.Merge- keeps current DB file and upserts aircraft records byModeS.
ADSBX note:
basic-ac-db.json.gzincludes nativemilflag support (military classification).- There is no dedicated
governmentfield in this dataset.
Recommended process:
- Confirm source URL is valid and in expected format.
- Run import.
- Check server logs.
- Verify results on map/list.
AircraftDB Editor and custom photos
Dedicated guide:
Quick summary:
ModeSmust stay unique (duplicate create/update is blocked),- editor provides
Load existing aircraftpath for duplicate ICAO conflicts, - custom aircraft photo can be uploaded per ICAO and has priority over PlaneSpotters.
5. Configuration Backup
This section provides:
- settings export,
- settings import.
After importing configuration:
- verify ports,
- verify binding,
- restart service if required.
6. Danger Zone
Clear Application Data removes critical data (configuration, users, mappings, database).
Use only when:
- performing full instance reset,
- current backups exist,
- irreversible data loss is accepted.