Skip to main content

Log Analyzer

Drop in an AetherSDR log or a support bundle and this page lists the known problems it finds, what each one means, and where the fix is documented.

Your log stays on your computer. The analysis runs entirely in your browser. The file is never uploaded, and this page sends nothing anywhere. AetherSDR already redacts addresses, serial numbers and passwords from its logs.

Find your log

  • Help → Support & Diagnostics... shows the log and opens its folder. Use the newest aethersdr-*.log file.
  • Help → File an Issue... builds a support bundle (support-bundle-*.zip in the support folder next to the logs). You can drop the .zip here as it is.
  • Log folders: Linux ~/.config/AetherSDR/logs/, macOS ~/Library/Preferences/AetherSDR/logs/, Windows %LOCALAPPDATA%\AetherSDR\logs\. See Support and Logging.

Check a log

Drag a .log, .txt or support-bundle .zip file here, or

The file is read by your browser only.

Results

No log checked yet.

What this page checks for (40 checks)
CheckSeverityDocs
Radio discovery could not listen on UDP port 4992ProblemTroubleshooting → No radio appears under on this network
No discovery broadcasts were receivedWarningTroubleshooting → No radio appears under on this network
The radio refused the connection (for example F3000001)ProblemTroubleshooting → The radio refuses the connection
Another station disconnected this sessionWarningMulti flex → Troubleshooting
multiFLEX is off and other clients are connectedInfoTroubleshooting → A connected stations dialog appears when you connect
The connection to the radio failedProblemManual connection → The probe fails
The radio stopped answering and was disconnectedWarningLow bandwidth connections → Troubleshooting
Radio firmware v3.x is not supportedProblemFirmware update → Firmware compatibility
No spectrum data (VITA-49 UDP) arrived from the radioProblemLow bandwidth connections → Audio works but the spectrum and waterfall stay empty over a vpn
The local UDP stream port could not be openedProblemManual connection → Audio works over a vpn but the spectrum and waterfall stay empty
The UDP receive buffer was capped by the systemInfoLow bandwidth connections → The vita 49 rx buffer says it was capped
SmartLink sign-in failedProblemSmartlink setup → The radio is not listed after you sign in
SmartLink certificate does not match the pinned oneProblemSmartlink setup → A certificate mismatch warning appears
The SmartLink connection to the radio failedProblemSmartlink setup → The radio is listed but you cannot connect
The speaker output failedProblemTroubleshooting → No audio from the speakers
The microphone input could not be openedProblemBefore you transmit → Transmit audio is missing with mic source set to pc
PipeWire is installed but its client configuration is missingWarningLinux → Pc audio misbehaves on a pipewire system
A DAX audio device could not be createdProblemDax virtual audio → The program hears no audio
The radio refused a DAX receive streamProblemDax virtual audio → The program hears no audio
The DAX transmit stream could not be createdProblemDax virtual audio → Transmit audio does not reach the radio
A DAX IQ device could not be createdProblemDax iq streaming → A program sees no aethersdr dax iq device
A CAT port is already in useProblemCat control → The clients column shows
The TCI server could not startProblemTci server → The server wont start because port 50001 is in use
The GPU renderer failed ("Spectrum renderer unavailable")ProblemGpu rendering → A spectrum renderer unavailable card covers the panadapter
Software rendering is forcedInfoGpu rendering → The display is correct but slow and about says cpu qrhi
X11 errors were suppressed (XWayland)WarningTroubleshooting → Aethersdr crashes opening a dialog under xwayland glx badaccess
The settings database is locked by another processProblemSettings and backups → Aethersdr reports that it cannot save settings
The settings database cannot be opened or savedProblemSettings and backups → Aethersdr reports that it cannot save settings
Settings were written by a newer AetherSDRWarningSettings and backups → An older version of aethersdr doesnt save your changes
The settings database was corrupt and was restoredWarningSettings and backups → How the store protects itself
NR2 started without FFTW wisdomInfoNr2 noise reduction → Fftw wisdom first use
BNR: this GPU cannot run the NVIDIA denoiserProblemBnr gpu noise removal → Bnr is greyed out bnr requires an nvidia rtx 40 series or later gpu
BNR: the model pack for this GPU is missingWarningBnr gpu noise removal → Bnr is greyed out no bnr pack for your gpu yet
Hermes-Lite 2: the UDP socket could not be openedProblemHermes lite 2 → Connecting
Hermes-Lite 2: the receive stream went silentWarningHermes lite 2 → Connecting
Icom: the radio rejected the user name or passwordProblemNetworked icom → Connect by ip fails with a handshake error
Icom: the radio did not answerProblemNetworked icom → The radio is in standby and does not answer
Some log lines were droppedInfoSupport and logging → The log has no detail about your problem
A system library is missing (error while loading shared libraries)ProblemTroubleshooting → Error while loading shared libraries libopenglso0
The system C library (glibc) is too oldProblemTroubleshooting → The appimage does not run on raspberry pi os bookworm

Each check matches a message AetherSDR itself writes, and names the source line it comes from. Missing a problem you hit? Open an issue.