Troubleshooting
This section covers common issues when using V2ROOT and how to resolve them.
Installation Issues
Problem: pip install v2root fails with “No matching distribution found”.
Solution: - Ensure you have Python 3.8 or higher:
python --version
Check your internet connection or try a different PyPI mirror:
pip install v2root --index-url https://pypi.org/simple
Problem: libv2root.dll or libv2root.so not found after installation.
Solution:
Verify that the shared library is included in the package:
pip show v2root ls -l $(python -c "import v2root; print(v2root.__path__[0])")/lib
If missing, reinstall the package or manually place the library in the
lib/directory.Alternative solution for Linux: Download the pre-compiled static library and specify its path:
# Download the static library wget https://github.com/V2RayRoot/V2Root/releases/download/V1.2.0/libv2root-static-1.2.0.so # Move it to a suitable location sudo mkdir -p /usr/local/lib/v2root sudo mv libv2root-static-1.2.0.so /usr/local/lib/v2root/libv2root.so
Then initialize V2ROOT with the custom library path:
from v2root import V2ROOT # Specify the custom library path v2 = V2ROOT(lib_path="/usr/local/lib/v2root/libv2root.so")
For Windows: If you encounter library issues, you’ll need to compile the library yourself. Download the source code:
# Clone the repository git clone https://github.com/V2RayRoot/V2Root.git cd V2Root/v2root/lib # Compile using MSYS2/MinGW make -f Makefile.win
Then specify the compiled library path when initializing V2ROOT:
from v2root import V2ROOT # Specify the custom library path v2 = V2ROOT(lib_path="C:\\path\\to\\your\\compiled\\libv2root.dll")
Compilation Issues
Problem: Compilation of libv2root.dll fails with “command not found” for x86_64-w64-mingw32-gcc.
Solution: - Ensure MSYS2 is installed and the MinGW64 environment is set up:
pacman -S mingw-w64-x86_64-gcc
Add MinGW64 to your PATH:
export PATH=$PATH:/mingw64/bin
Compile again using the correct compiler.
Runtime Issues
Problem: start_proxy fails with “Invalid configuration string”.
Solution:
- Check the configuration string format (see Supported Configuration Options).
- Example valid VLESS string: vless://uuid@example.com:443?type=tcp&security=tls&sni=example.com
Problem: Proxy starts but no connection is established.
Solution: - Verify the HTTP/SOCKS ports are not in use:
netstat -tuln | grep 10808
Ensure the V2Ray executable is accessible and correctly configured (see Installation).
Virtual Environment Issues
Problem: Activating virtual environment in PowerShell fails with a security error.
Solution: - Change the execution policy:
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned
Or activate in CMD:
.\venv\Scripts\activate.bat
Error Code Issues
This section explains common V2Ray error codes, their causes, and solutions. Always check the v2root.log file in your project directory for detailed error messages to identify the specific issue.
Error -1: General Error
What is Error Code -1?
Error Code -1 is a “General Error” in V2Root, meaning something unexpected prevented the program from completing your request. This is a catch-all error for issues like missing files, insufficient permissions, or system misconfigurations when processing your configuration string (e.g., vless://, vmess://, ss://).
Why Does This Happen?
This error can occur due to:
- The configuration string is invalid or cannot be processed to create config.json.
- On Linux, V2Ray is not installed or is outdated.
- The program lacks permissions to access files or network resources.
- The V2Root library file (libv2root.dll on Windows, libv2root.so on Linux) is missing or inaccessible.
- Conflicts with antivirus or firewall software.
How to Fix It
Follow these steps carefully to resolve the issue:
Validate the Configuration String: - Ensure your configuration string starts with a supported protocol:
vless://vmess://ss://
Example valid string:
vless://user-id@server-address:443?security=tls&type=tcp#MyVPN
Check for typos in the user ID, server address, or port. Contact your VPN provider for a correct string if unsure.
Verify V2Ray Installation (Linux Only): - Check if V2Ray is installed:
v2ray versionIf missing or outdated, install the latest version:
For Ubuntu/Debian:
sudo apt update sudo apt install v2ray
For CentOS/RHEL:
sudo yum install v2ray
For other distros, download from the official V2Ray website.
Check V2Root Library File:
On Windows, ensure
libv2root.dllexists in the V2Root folder, for example:C:\V2Root\libv2root.dll
Replace
C:\V2Root\with the actual folder where you installed V2Root.Check if it exists:
dir C:\V2Root\libv2root.dll
If missing, reinstall V2Root or contact support.
Alternative: Download the source and compile it yourself (see Installation Issues section above).
On Linux, ensure
libv2root.soexists, for example:/usr/local/lib/v2root/libv2root.so
Replace
/usr/local/lib/v2root/with the actual V2Root folder path.Check if it exists:
ls /usr/local/lib/v2root/libv2root.soEnsure it’s readable:
chmod +r /usr/local/lib/v2root/libv2root.so
If missing, contact support or download the pre-compiled static library:
wget https://github.com/V2RayRoot/V2Root/releases/download/V1.2.0/libv2root-static-1.2.0.so sudo mkdir -p /usr/local/lib/v2root sudo mv libv2root-static-1.2.0.so /usr/local/lib/v2root/libv2root.so
Then initialize V2ROOT with
lib_path="/usr/local/lib/v2root/libv2root.so".
Check Port Availability:
Ensure ports 10808 (HTTP) and 1080 (SOCKS) are free:
On Linux:
netstat -tuln | grep 10808 netstat -tuln | grep 1080
If in use, find the program:
sudo lsof -i :10808
Stop it or change ports in your script.
On Windows:
netstat -an | findstr 10808 netstat -an | findstr 1080
If used, close the program via Task Manager or change ports.
Test Internet Connectivity:
Check internet:
ping 8.8.8.8
If no response, restart your router or contact your ISP.
Test the server in your configuration string:
ping server-addressReplace
server-addresswith the address from your string. If it fails, contact your VPN provider.
Check Firewall and Antivirus:
On Windows, allow
v2root.pyandC:\V2Root\libv2root.dll(use your path) in Windows Defender:Settings > Update & Security > Windows Security > Virus & Threat Protection > Manage Settings > Exclusions.
On Linux, allow ports:
sudo ufw allow 10808 sudo ufw allow 1080 sudo ufw status
Inspect the Log File:
Open
v2root.logand look for:“Port already in use” (free ports).
“Network unreachable” (check internet/server).
“Invalid config” (check configuration string).
View log:
cat v2root.log
Error -2: Service Error
What is Error Code -2?
Error Code -2 is a “Service Error” in V2Root, indicating that the V2Ray program failed to start or couldn’t connect to the internet after processing your configuration string. This error relates to issues with launching the V2Ray core or establishing network connectivity.
Why Does This Happen?
Common causes include:
- On Linux, V2Ray is not installed or is outdated, preventing the service from starting.
- Network ports (e.g., 10808, 1080) are already in use by another program.
- A firewall or antivirus is blocking V2Ray’s network access.
- Internet connectivity issues (e.g., no internet or server downtime).
- The configuration string caused an invalid config.json to be generated.
How to Fix It
Follow these detailed steps to resolve the issue:
Validate the Configuration String: - Ensure your configuration string starts with:
vless://vmess://ss://
Example valid string:
vless://user-id@server-address:443?security=tls&type=tcp#MyVPN
Check for typos in the user ID, server address, or port. Contact your VPN provider for a correct string.
Verify V2Ray Installation (Linux Only): - Check if V2Ray is installed:
v2ray versionIf missing or outdated, install the latest version (see Error -1, step 2 above).
Check V2Root Library File: - Follow the same steps as Error -1, step 3 above. If missing, see the Installation Issues section.
Check Port Availability: - Follow the same steps as Error -1, step 4 above.
Test Internet Connectivity: - Follow the same steps as Error -1, step 5 above.
Check Firewall and Antivirus: - Follow the same steps as Error -1, step 6 above.
Inspect the Log File: - Follow the same steps as Error -1, step 7 above.
Error -3: Config Error
What is Error Code -3?
Error Code -3 is a “Config Error” in V2Root, meaning the V2Ray configuration string you provided (e.g., vless://, vmess://, ss://) is incorrect, malformed, or incompatible. This prevents V2Root from generating a valid config.json file, which stops V2Ray from starting or connecting properly.
Why Does This Happen?
This error can occur because:
- The configuration string has an invalid format or missing components (e.g., wrong protocol, missing user ID, or incorrect server address).
- The server address, port, or user ID in the configuration string is wrong or outdated.
- The V2Ray protocol in the string (e.g., vless, vmess) is not supported by your version of V2Ray or V2Root.
- The program failed to parse the configuration string due to a bug or unsupported characters.
- The VPN provider gave you an incorrect or expired configuration string.
How to Fix It
Follow these detailed steps to resolve the issue:
Validate the Configuration String: - Ensure your configuration string starts with a supported protocol:
vless://vmess://ss://
Example of a valid string: .. code-block:: none
vless://user-id@server-address:443?security=tls&type=tcp#MyVPN
Check for: - User ID: A valid UUID or identifier (e.g.,
123e4567-e89b-12d3-a456-426614174000). - Server Address: A correct IP address (e.g.,192.168.1.1) or domain (e.g.,vpn.example.com). - Port: A number like443or1080. - Parameters: Correct settings likesecurity=tlsortype=tcp.Compare your string with examples from your VPN provider. Fix any typos or missing parts.
Contact Your VPN Provider: - If you’re unsure about the configuration string, send it to your VPN provider (remove sensitive parts like the user ID if needed) and ask them to verify:
Is the protocol (
vless,vmess,ss) correct?Is the server address and port still active?
Are the user ID and other parameters valid?
Request a new configuration string if yours is outdated or incorrect.
Test the Server Address: - Extract the server address from your configuration string (e.g.,
server-addressinvless://user-id@server-address:443). - Test if it’s reachable:ping server-addressIf the ping fails, the server may be down or the address is wrong. Ask your VPN provider for an alternative server.
Test a Different Configuration String: - Ask your VPN provider for another configuration string (e.g., a different server or protocol). - Update your script to use the new string (e.g., pass it to
set_config_string) and rerunv2root.py.Update V2Ray (Linux Only): - An outdated V2Ray version may not support newer protocols in the configuration string. Check the version:
v2ray versionIf it’s missing or old, update or install V2Ray (see Error -1, step 2 above).
Check Windows Setup: - On Windows, V2Ray is bundled with V2Root, so no separate installation is needed. - Ensure the file
libv2root.dllis in the same folder asv2root.pyor in thelib/build_winsubdirectory. - If missing, see the Installation Issues section above.Inspect the Log File: - Open
v2root.login the same folder asv2root.pywith a text editor (e.g., Notepad on Windows,nanoon Linux). - Look for errors related to the configuration string orconfig.jsongeneration, such as:“Invalid configuration string” (check string format).
“Failed to parse JSON” (indicates V2Root couldn’t create a valid
config.jsonfrom the string).“Unknown protocol” (use a supported protocol like
vlessorvmess).“Server rejected” (wrong user ID, server address, or port).
View the log on Linux:
cat v2root.logIf the log mentions
config.json, it may show the generated file’s contents. Check for errors like missing fields or invalid JSON syntax.
Reinstall V2Root: - If the program is failing to process the configuration string, there might be a bug or corrupted files. - Delete the V2Root folder and redownload the latest version from the official V2Root release page. - Extract and rerun
v2root.pywith your configuration string.
Error -4: Connection Error
What is Error Code -4?
Error Code -4 is a “Connection Error” in V2Root, meaning the program couldn’t connect to the V2Ray server specified in your configuration string or use the network. This error occurs after V2Root generates config.json from the string and tries to establish a connection, indicating network or server issues.
Why Does This Happen?
Possible causes include:
- The server address or port in the configuration string is incorrect or outdated.
- The V2Ray server is down, unreachable, or rejecting connections.
- Network ports (e.g., 10808 for HTTP, 1080 for SOCKS) are blocked by a firewall, router, or ISP.
- No internet connection or an unstable network.
- Other VPN or proxy software is interfering with V2Root’s network access.
- The generated config.json has issues due to errors in the configuration string processing.
How to Fix It
Follow these detailed steps to resolve the issue:
Verify Server Address and Port in the Configuration String:
Check your configuration string (e.g.,
vless://user-id@server-address:443?security=tls&type=tcp#MyVPN).Ensure the server address (e.g.,
server-address) and port (e.g.,443) are correct.Test the server’s reachability:
ping server-addressIf the ping fails, the server may be down or the address is wrong. Contact your VPN provider to confirm the server details or get a new configuration string.
Test a Different Configuration String: - Ask your VPN provider for an alternative configuration string with a different server or port. - Update your script to use the new string (e.g., pass it to
set_config_string) and rerunv2root.py.Check Internet Connectivity: - Ensure your internet is working:
ping 8.8.8.8
If there’s no response, troubleshoot your network:
Restart your router or modem.
Check Wi-Fi or Ethernet connection.
Contact your ISP if the issue persists.
Verify Port Availability: - V2Root uses ports 10808 (HTTP) and 1080 (SOCKS) by default for local connections. Ensure they’re not blocked or in use. - Follow the same steps as Error -1, step 4 above.
Check Firewall and Antivirus Settings: - On Windows, ensure Windows Defender or other antivirus allows
v2root.pyandlibv2root.dll:Go to Settings > Update & Security > Windows Security > Virus & Threat Protection > Manage Settings > Exclusions > Add an exclusion for both files.
On Linux, check if
ufwor another firewall is blocking ports:sudo ufw status
Allow V2Root’s ports:
sudo ufw allow 10808 sudo ufw allow 1080
Check your router’s firewall settings. If behind NAT, ensure ports 10808 and 1080 are forwarded.
If your ISP blocks VPN ports, ask your VPN provider for a configuration string using a different port (e.g., 443).
Inspect the Log File: - Open
v2root.login the same folder asv2root.pywith a text editor. - Look for errors related to the connection orconfig.jsongeneration, such as:“Connection refused” (wrong server address/port or server down).
“Network timeout” (internet issue or server unreachable).
“Failed to parse config” (indicates an issue with the generated
config.jsondue to the configuration string).
View the log on Linux:
cat v2root.log
Check for VPN/Proxy Conflicts: - Ensure no other VPN or proxy software (e.g., OpenVPN, NordVPN) is running, as they may interfere with V2Root. - On Windows, disable other VPNs:
Settings > Network & Internet > VPN > Disconnect any active VPNs.
On Linux, stop other VPN services:
sudo systemctl stop openvpn
Update V2Root and V2Ray: - On Linux, ensure V2Ray is up-to-date to handle the configuration string and network protocols:
v2ray version sudo apt update sudo apt install v2ray
On Windows, ensure you have the latest V2Root version:
Delete the V2Root folder and redownload from the official V2Root release page.
Verify
libv2root.dllis present in the same folder asv2root.pyor inlib/build_win.
Error -5: Initialization Error
What is Error Code -5?
Error Code -5 is an “Initialization Error” in V2Root, meaning the program couldn’t start V2Ray due to missing or misconfigured components when processing your configuration string. This occurs during the setup phase.
Why Does This Happen?
Possible causes include:
On Linux, V2Ray is not installed system-wide.
The V2Root library (
libv2root.dllon Windows,libv2root.soon Linux) is missing or inaccessible.Missing system libraries (e.g.,
libjanssonon Linux).Insufficient permissions for V2Root files.
Incompatible system environment.
How to Fix It
Follow these steps:
Validate the Configuration String:
Ensure it starts with:
vless://vmess://ss://
Example:
vless://user-id@server-address:443?security=tls&type=tcp#MyVPN
Check for typos. Contact your VPN provider for a valid string.
Verify V2Ray Installation (Linux Only): - Check:
v2ray versionIf missing or outdated, install the latest V2Ray (see Error -1, step 2 above).
Check V2Root Library File: - Follow the same steps as Error -1, step 3 above. If missing, see the Installation Issues section.
Check for Missing Libraries (Linux Only): - Verify dependencies for
libv2root.so:ldd /usr/local/lib/v2root/libv2root.soReplace the path with your
libv2root.solocation.
Install missing libraries, e.g.:
sudo apt install libjansson-dev libc6
Verify File Permissions: - Linux: Ensure
v2root.pyandlibv2root.soare accessible:ls -l v2root.py ls -l /usr/local/lib/v2root/libv2root.so chmod +x v2root.py chmod +r /usr/local/lib/v2root/libv2root.so
Use your
libv2root.sopath.
Windows: Ensure
v2root.pyandC:\V2Root\libv2root.dllaren’t blocked:Right-click > Properties > Unblock (if visible).
Inspect the Log File: - Open
v2root.logfor errors like:“V2Ray core not found” (install V2Ray).
“Library not found” (check
libv2root.dllorlibv2root.so).“Invalid config” (check configuration string).
View:
cat v2root.log
Update System: - Windows: Run Windows Update. - Linux:
sudo apt update && sudo apt upgrade
Error -6: Proxy Error
What is Error Code -6?
Error Code -6 is a “Proxy Error” in V2Root, meaning the program couldn’t set or clear your system’s proxy settings after processing your configuration string. This affects V2Root’s ability to configure V2Ray as a proxy.
Why Does This Happen?
Causes include:
Insufficient permissions to modify proxy settings.
Other VPN/proxy software interfering.
Corrupted or locked system proxy settings.
Antivirus blocking proxy changes.
Issues with the generated
config.jsonfrom the configuration string.
How to Fix It
Follow these steps:
Validate the Configuration String:
Ensure it starts with:
vless://vmess://ss://
Example:
vless://user-id@server-address:443?security=tls&type=tcp#MyVPN
Check typos. Contact your VPN provider for a valid string.
Run as Administrator:
Windows: Right-click
v2root.py> “Run as administrator”.Or PowerShell as admin:
python v2root.py
Linux:
sudo python3 v2root.py
Ensure executable:
chmod +x v2root.py
Check V2Root Library File: - Follow the same steps as Error -1, step 3 above. If missing, see the Installation Issues section.
Check for Conflicting Software: - Close other VPNs/proxies. - Windows: Settings > Network & Internet > Proxy > No manual proxy unless needed. - Linux:
sudo systemctl stop openvpn
Reset Proxy Settings: - Windows:
netsh winhttp reset proxy
Restart PC.
Linux:
gsettings reset org.gnome.system.proxy
Check Antivirus: - Windows: Add exceptions for
v2root.pyandC:\V2Root\libv2root.dll(your path) in Windows Defender. - Linux: Ensure no security software blocks V2Root.Inspect the Log File: - Open
v2root.logfor:“Permission denied” (run as admin).
“Proxy setting failed” (check conflicts).
“Invalid config” (check configuration string).
View:
cat v2root.log
Error -7: Process Already Running
What is Error Code -7?
Error Code -7 is a “Process Already Running” error in V2Root, meaning you attempted to start a new V2Ray connection while another V2Ray process is still active. V2Root prevents multiple instances from running simultaneously to avoid conflicts with network ports, system resources, and proxy settings.
Why Does This Happen?
This error occurs when: - You previously started V2Ray and forgot to stop it before starting a new connection. - A previous V2Ray process didn’t terminate properly (e.g., due to a crash or forceful program closure). - The process ID (PID) is stored in the system registry (Windows) but the actual process might still be running in the background. - You’re running multiple scripts or programs that try to start V2Ray simultaneously. - On Windows, the registry contains a PID from a previous session that wasn’t cleaned up.
How to Fix It
Follow these detailed steps to resolve the issue:
Stop the Existing V2Ray Process Using V2Root:
The safest way is to use V2Root’s built-in stop function in your script:
from v2root import V2ROOT v2root = V2ROOT() v2root.stop()
This will properly terminate the V2Ray process and clean up proxy settings.
Check for Running V2Ray Processes:
On Windows:
Open Task Manager (press
Ctrl+Shift+Esc).Look for processes named
v2ray.exeorv2ray.Right-click and select “End Task” to terminate them.
Alternatively, use PowerShell:
tasklist | findstr v2ray taskkill /IM v2ray.exe /F
On Linux:
Open a terminal and check for V2Ray processes:
ps aux | grep v2ray
Kill the process using its PID (replace
12345with the actual PID):sudo kill -9 12345
Or kill all V2Ray processes:
sudo pkill v2ray
Clear Registry Data (Windows Only):
V2Root stores the PID in the Windows Registry under
HKEY_CURRENT_USER\Software\V2ROOT.Open Registry Editor:
Press
Win+R, typeregedit, and press Enter.Navigate to:
HKEY_CURRENT_USER\Software\V2ROOTLook for a value named
V2RayPID.Right-click and delete it.
Alternatively, use PowerShell:
Remove-ItemProperty -Path "HKCU:\Software\V2ROOT" -Name "V2RayPID" -ErrorAction SilentlyContinue
Wait a Few Seconds:
After stopping the process, wait 5-10 seconds before starting V2Ray again.
This ensures the process fully terminates and releases network resources.
Restart Your Script:
After stopping the existing process, run your script again:
python v2root.pyV2Root should now start successfully without the -7 error.
Check for Port Conflicts:
The previous V2Ray process might still be holding ports 2300 (HTTP) or 2301 (SOCKS).
On Windows:
netstat -an | findstr 2300 netstat -an | findstr 2301
If ports are in use, find and terminate the program using Task Manager.
On Linux:
netstat -tuln | grep 2300 netstat -tuln | grep 2301
If ports are occupied, find the process:
sudo lsof -i :2300 sudo kill -9 <PID>
Inspect the Log File:
Open
v2root.login the same folder as your script.Look for entries related to process management:
“V2Ray process already running with PID: …” (note the PID and terminate it).
“Failed to stop V2Ray process” (indicates the process is stuck).
View the log:
cat v2root.log
Restart Your Computer (Last Resort):
If the process is stuck and won’t terminate, restart your computer.
This will forcefully close all processes and clear any registry or system locks.
How to Avoid This Error in the Future
To prevent Error -7 from happening again:
Always Stop V2Ray Before Starting a New Connection:
Add a stop command before starting:
from v2root import V2ROOT v2root = V2ROOT() v2root.stop() # Stop any existing process v2root.set_config_string(config_str) v2root.start() # Start with new configuration
Use Try-Finally Blocks:
Ensure V2Ray stops even if your script crashes:
from v2root import V2ROOT v2root = V2ROOT() try: v2root.set_config_string(config_str) v2root.start() # Your code here finally: v2root.stop() # Always stop when done
Check Process Status Before Starting:
Verify no V2Ray process is running before starting a new one:
import subprocess # Check for existing process result = subprocess.run(['tasklist'], capture_output=True, text=True) # Windows # result = subprocess.run(['ps', 'aux'], capture_output=True, text=True) # Linux if 'v2ray' in result.stdout.lower(): print("V2Ray is already running. Stopping it first...") v2root.stop()
Don’t Run Multiple Scripts Simultaneously:
Avoid running multiple Python scripts that use V2Root at the same time.
If you need to test multiple configurations, stop V2Ray between tests.
Still Stuck?
If you’ve tried all the steps and the issue persists, we’re here to help! Contact us with the following details:
The script file you’re running (e.g.,
v2root.py).The
v2root.logfile from the same folder.Your operating system (Windows or Linux).
A description of when the error started (e.g., “after a crash” or “when running multiple scripts”).
Report the issue on:
Telegram: @Sepehr0Day
Unknown Error Codes
What are Unknown Error Codes?
Unknown Error Codes in V2Root are any errors not explicitly identified as -1 through -7. These are unexpected issues that may arise due to bugs, system incompatibilities, or unique configurations not handled by V2Root’s error reporting.
Why Does This Happen?
Possible causes include: - A bug in V2Root or V2Ray. - System-specific issues (e.g., outdated OS, missing dependencies). - Conflicts with other software or drivers. - Invalid or corrupted configuration string causing unhandled errors. - Hardware or network issues not detected by V2Root.
How to Fix It
Follow these steps to troubleshoot:
Inspect the Log File:
Open
v2root.login the same folder asv2root.pywith a text editor.Look for detailed error messages, such as:
Specific error codes or messages not listed as -1 to -7.
Stack traces or system errors (e.g., memory issues, library failures).
Messages about configuration or network failures.
View the log on Linux:
cat v2root.logNote any specific errors for support.
Validate the Configuration String: - Follow the same steps as Error -1, step 1 above.
Verify V2Ray Installation (Linux Only): - Follow the same steps as Error -1, step 2 above.
Check V2Root Library File: - Follow the same steps as Error -1, step 3 above. If missing, see the Installation Issues section.
Restart the Program: - Close V2Root and rerun
v2root.py:Windows:
python v2root.py
Linux:
python3 v2root.py
If the error persists, try restarting your computer.
Update System and Software: - Windows: Run Windows Update to ensure all system components are current. - Linux:
sudo apt update && sudo apt upgrade
Reinstall V2Root if issues persist:
Delete the V2Root folder and redownload from the official V2Root release page.
Check for Conflicts: - Ensure no other VPN, proxy, or network software is running. - Windows: Settings > Network & Internet > VPN > Disconnect any active VPNs. - Linux:
sudo systemctl stop openvpn
Additional Resources
Contact support via Telegram (@Sepehr0Day) or GitHub Issues.
Include your script (e.g.,
v2root.py), configuration string (remove sensitive parts),v2root.log, and OS when reporting issues.