This guide explains how to use the Qoder IDE diagnostic script to troubleshoot startup and connectivity issues with Qoder IDE. The script automatically collects critical system information, including environment details, network settings, Qoder IDE service status, and relevant logs, enabling quick diagnosis and resolution of common problems.
Before running the diagnostic script, ensure the following:
Once the script finishes:
Prerequisites
Before running the diagnostic script, ensure the following:
- Operating System: Windows
- Permissions: Run the script with administrator privileges for full access to system settings and logs.
- Script file: Download and save the windows_Qoder.bat script as a
.batfile (example:qoder_Debug.bat). - Installation path: Confirm that Qoder IDE is installed in the default directory
C:\Users\<YourUsername>\.qoder.
Run the diagnostic script
Step 1: Run the script
- Locate the saved
.batfile.
qoder_Debug.bat
- Double-click the file to execute the script.
- The script will run automatically, collecting system and application data.
Step 2: View the generated log
Once the script finishes:
- A compressed archive (ZIP) containing the collected log files and key configuration files will be automatically generated.
The filename follows this format:qoder-diagnosis_YYYYMMDD_HHMMSS.zip
Example: _qoder-diagnosis_Sat_2025-10-11_16-00-03.93.zip - The main log file is included in the archive, with the naming format:
Qoder_Log_YYYYMMDD_HHMMSS.txt
Example: _Qoder_Log_20250405_143022.txt - You can send the entire diagnostic ZIP package to the Qoder official team to assist with issue investigation and troubleshooting.
Common issues
| Issue type | Issue | Solution |
|---|---|---|
| Network | Check proxy settings | The script checks whether a proxy is enabled. Review the section [Network Settings 0x0 means proxy is disabled] to confirm expected behavior.If a proxy is in use, manually configure the network proxy for Qoder IDE in the settings. |
| Qoder IDE Server Status | Existence of Qoder.exe | The script verifies if Qoder.exe exists. If an error occurs: 1. Check the installation path. 2. Delete the .qoder directory. 3. Restart your IDE to regenerate the directory. |
| Version and startup test | Check the [Version Test] and [Start Qoder IDE] sections to confirm: * Qoder IDE version * Connection to the public server If it shows "failed," use the URL from the error message to configure proxy access in settings. | |
| Qoder.exe running but logon fails | Add the executable to Windows Firewall whitelist: Path: 1. windows：C:\Users\用户名\AppData\Local\Programs\Qoder\resources\app\resources\bin`CPU_architecture_64_system \Qoder.exe<br/>2. Mac：/Applications/Qoder.app/Contents/Resources/app/resources\bin\CPU_architecture_64_system`\QoderSteps: Control Panel → System and Security → Windows Defender Firewall → Allowed Apps → Allow another app Then retry login. | |
| System compatibility | System and hardware information | The script collects: * OS version (e.g., Windows 10/11) * CPU model Check [Operating System Information] to ensure your system meets Qoder IDE's requirements: * Windows 10 or later (64-bit) * x86_64-compatible CPU |
| Log analysis | Qoder IDE application logs | The generated log includes the last 80 lines of qoder.log.Use this to identify runtime errors, warnings, or connection issues. |
| Directory structure and file size | The script lists the full directory structure and file sizes under .qoder. Use this to: * Check disk usage. * Verify file integrity (such as missing or abnormally small files). | |
| Note | Binary execution restrictions | Some corporate environments restrict or block binary execution, which may prevent Qoder IDE from running. If the app fails to start, contact your IT department for permission adjustments. |
| Unresolvable issues | Issues beyond self-troubleshooting | If you cannot resolve the issue, contact us at: contact@qoder.com. Please attach the generated log file: Qoder_Log_YYYYMMDD_HHMMSS.txt for faster support. |