🔧 Troubleshooting
This document provides solutions for problems that may occur while using SRT Probe.
Cannot Connect
Symptom: Test stays “Disconnected” after starting
Solutions:
- Verify that SRT Probe is allowed in the firewall
- Confirm the port number is correct (use the same port number on sender and receiver)
- Verify one side is waiting in Listener mode
- Confirm the IP address is correct
Statistics Not Displayed
Symptom: Connection succeeds but RTT or throughput is not displayed
Solutions:
- Verify data is actually being sent and received
- Confirm running in Sender mode (statistics may not display with Receiver only)
- Check log output for errors
Language Does Not Change
Symptom: UI does not change after selecting a language
Solutions:
- Exit the app completely and restart
- Check the settings file:
C:\Users\[username]\.srt-probe\settings.json
- If the settings file is corrupted, delete it and restart
App Won’t Start
Symptom: Nothing happens when double-clicking the icon
Solutions:
- Check Windows version (Windows 10/11 required)
- Verify Microsoft Visual C++ Redistributable Package is installed
- Check Event Viewer for error logs
Frequently Asked Questions (FAQ)
Q1: Language change is not reflected
A: Please completely exit the app and restart. The settings file will be loaded.
A: In Windows Defender Firewall, add SRT Probe.exe to the allowed list.
Steps:
- Open Windows Security
- Select “Firewall & network protection”
- Click “Allow an app through firewall”
- Find “SRT Probe” and check both Private and Public
Q3: RTT is always displayed as 0ms
A: Data may not be transmitted yet. Verify you are connected in Sender mode.
Q4: Presets are not saved
A: Verify you have write permission to the settings file folder. It is usually C:\Users\[username]\.srt-probe\.
Q5: Cannot connect (stays Disconnected)
A: Please check the following:
- Is the other side started first? (For Listener mode)
- Are the IP address and port number correct?
- Is the port open in the firewall?
- Is the network connected?
Other Issues
If the above does not resolve your issue, please report the problem at GitHub Issues.