Skip to main content

Troubleshooting

1. /admin returns Invalid url

Most common causes:

  1. port conflict,
  2. admin is running on a different port than expected,
  3. reverse proxy path/port mismatch.

Check:

  1. which process listens on admin port,
  2. AdminPort and WebServerPort values in config,
  3. curl -I http://<host>:<admin-port>/admin after restart.

2. Radar works locally but not on LAN

Check:

  1. Network Binding is set to all interfaces,
  2. host firewall rules,
  3. service is listening on 0.0.0.0:<port>.

Linux example:

ss -ltnp | rg ':8080|:5000|:8085'
curl -I http://<lan-ip>:<port>/admin

3. AircraftList.json becomes empty after some time

Possible causes:

  1. feed connection loss,
  2. background exception stopping host,
  3. overload or unstable upstream data patterns.

Check:

  1. service logs (journalctl -u vrsx),
  2. feed status and message throughput,
  3. process uptime after errors.

4. Aircraft positions jump backward or flicker

Common causes:

  1. MLAT instability,
  2. low-quality feed or high jitter,
  3. mixed sources without stable source-priority logic.

Diagnostic flow:

  1. compare same feed in VRS X vs reference VRS,
  2. test single feed instead of All feeds,
  3. compare JSON output over identical bbox/time intervals.

5. Resource import says success, but no visual effect

  1. Verify Loaded counters.
  2. Verify CSV keys match asset names.
  3. Clear browser cache.
  4. Verify icon/type mapping and metadata consistency.
Back to top