DXChrono Desktop

Help → Troubleshooting

Quick checks first

• Confirm a license key is saved (Settings → License, or the first-run license dialog).
• Confirm your station callsign is set in Settings → Station (not NOCALL).
• Confirm your PC has internet access and your firewall allows DXChrono outbound connections.
• Press R to force a data refresh, then wait for normal refresh intervals from Settings → Data.
• If data is stale, verify your refresh intervals are not set very high.

Update checks (new version reminder)

The app compares your running version to a small file on desktop.dxchrono.com. It does not send your callsign or logbook data. If checks never seem to work:

• Confirm the PC has normal web access (try opening desktop.dxchrono.com in a browser).
• Some club or corporate networks block unknown HTTPS sites—ask the network admin to allow desktop.dxchrono.com, or run the check from home or phone hotspot once.
• Open Settings → Data, click Check for Updates, and read the message at the bottom of the Settings window (green = you are up to date; amber = the check could not finish).
• If you do not want automatic checks, turn off Check for app updates on the same tab and watch the download page for new releases.

Full options are described under Settings → Data → Software updates.

License: Activate or Validate fails

• Check that the key is pasted exactly (no extra spaces); copy from the purchase email again if unsure.
• Confirm the PC has internet access. A strict firewall or some shared networks can block license checks.
• Too many computers – A license key usually allows up to five PCs. If you see a device limit message, check your order email for how to manage activations, or contact where you bought DXChrono for help.
• If Validate license when app starts is on and something fails in the background, open Settings → License and use Validate or Activate to see the message in the app.

No data or map overlays updating

• Open Settings → Data and check refresh intervals (solar, bands, aurora, gray line, Cloudlog, ADIF Logbook, QRZ Logbook).
• If only one data source is missing, check that specific service endpoint and credentials.
• If everything is missing, check local network/firewall/proxy policy first.

Cloudlog test fails

• Use the base URL without a trailing slash (for example https://log.example.com).
• Generate/verify API key in Cloudlog (Admin → API Keys).
• If recent QSOs are empty, verify your public slug setup (if used).
• Test the same URL/API key from a browser or curl on the same machine.

QRZ Logbook: no markers or empty map pins

• Confirm Test on the QRZ tab succeeds (STATUS). FETCH needs Logbook API access on your QRZ account.
• Ensure Show QSOs on map is enabled on the QRZ tab.
• Map placement needs a gridsquare or lat/lon fields in the QSO record QRZ exports; if your log entries lack a locator, pins cannot be placed.
• Try a wider FETCH date span or higher FETCH max records if you expect contacts outside the default window.
• When running from a terminal, enable Print FETCH response preview on the QRZ tab (or set DXCHRONO_QRZ_DEBUG_ADIF=1) for a short ADIF preview in the console; the API key is not printed.

ADIF Logbook file: no markers or panel not updating

• Open Settings → ADIF and confirm Enable ADIF Logbook file is on.
• Check the file path (use Browse to avoid typos) and confirm the file exists and is readable.
• Ensure your ADIF records include a gridsquare or lat/lon fields for map pin placement.
• If your logger rotates files, update the path to the currently active .adi file.
• Verify Settings → Data → ADIF Logbook refresh interval is not set too high for your workflow.

N1MM data not appearing

• In DXChrono: Settings → N1MM, enable N1MM+ UDP and confirm port/address.
• In N1MM Logger+: Config → Config Ports and enable Broadcast Data to the same UDP port (default 12060).
• Ensure local firewall allows inbound UDP on that port.
• If using another host, verify the listen address and network route.

DX Cluster connects then drops

• Double-check host, port, and login callsign.
• Try a different cluster host to rule out server-side limits/outage.
• If your network has strict idle timeouts/NAT, shorter reconnect cycles may be expected.
• Use the DX command window (D) to confirm command/response flow.

PSK Reporter connected but no spots

• Set a real station callsign in Settings → Station (not NOCALL).
• Confirm you enabled at least one stream: “who's hearing me” and/or “who I'm receiving”.
• Verify MQTT host/port/TLS combination (1883 plain, 1884 TLS).
• Remember spot flow depends on on-air activity and report timing.

Linux/Wayland display issues

• If you see a black/flickering window, try windowed mode first (--windowed).
• Update GPU drivers and SDL/pygame packages from distro repos.
• On Raspberry Pi, test with the recommended build and current OS updates.

Crash logs and support info

DXChrono writes crash diagnostics to ~/.dxchrono/crash.log. If you report a bug, include:

• OS and app version
• What you were doing just before the issue
• Relevant section of ~/.dxchrono/crash.log
• Your integration settings summary (without sharing private API keys)