Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- With Windows v2rayN TUN and the system proxy off, a detached old Xray process may still own a local port and use a stale configuration.
- Read the process PID, path, start time, parent, owner, and listener PID before deciding whether to handle it.
- End only the exact process after confirming it is not part of the active client, its PID owns the relevant listener, and a backup is complete.
- Handle a process only after its exact PID is confirmed as the expected listener, it is not part of the active client, and necessary backups are complete. If explicit HTTP and SOCKS requests then pass, that verifies only the current session; process origin, the former endpoint failure, and TUN/startup/reboot persistence need separate checks.
Compare the selected node with the process behind the listener
If Windows v2rayN shows a new node but requests through the expected local port still appear to use an old node, identify which process owns that listener. The GUI selection, the active core configuration, and the system proxy state can differ. A node in the list does not prove that the process holding the port reloaded its configuration.
This diagnostic branch applies when TUN is off and the Windows system proxy is disabled. Test with an explicit HTTP or SOCKS local proxy request first; do not treat an ordinary browser request as the same test.
Read process identity and listener ownership
Read the PID, parent process, start time, executable path, and owner of relevant v2rayN and Xray processes. Compare each process ID with the OwningProcess value for the local listener. If an Xray process is not a child of the currently running v2rayN, or started before the current configuration was loaded, check its path and configuration source. These are clues, not proof that it can be removed.
The PowerShell commands below only read system state and do not stop processes. Output may contain account names, install paths, and listener ports; never publish it unredacted or include full command-line arguments.
Read core processes and local listener PIDs
powershellGet-CimInstance Win32_Process | Where-Object { $_.Name -match 'v2rayN|xray|sing-box' } | ForEach-Object { $owner = Invoke-CimMethod -InputObject $_ -MethodName GetOwner -ErrorAction SilentlyContinue; [pscustomobject]@{ Name=$_.Name; ProcessId=$_.ProcessId; ParentProcessId=$_.ParentProcessId; CreationDate=$_.CreationDate; ExecutablePath=$_.ExecutablePath; User=$owner.User } }
Get-NetTCPConnection -State Listen | Select-Object LocalAddress,LocalPort,OwningProcess
Confirm proxy mode and configuration source
Read the system proxy state in the same Windows user session and confirm whether the test explicitly connects to the local HTTP or SOCKS listener. If the system proxy is off, a direct browser request does not show that the local proxy is broken; test through the explicit listener first. Do not enable the system proxy to hide an old core that still owns the port.
If you need to compare core configuration, use the local client interface or a controlled local inspection to confirm whether the active node differs from the configuration used by the old process. Configuration may contain UUIDs, passwords, node hosts, and subscription data. Do not print or share its contents.
Handle a stale process only after an exact match
After saving necessary configuration backups, end a process through Windows Task Manager by its PID only when you have confirmed that the old Xray is not part of the current v2rayN process, its executable path and start time match the earlier session, and that same PID owns the expected local port. Recheck the PID and listener owner immediately before acting to avoid a reused PID or another app's core.
Do not terminate every Xray, v2rayN, or sing-box process by name, and do not recursively delete the core directory. If you cannot prove the process is stale, stop and preserve the state while checking its parent, owner, and configuration load time.
Restart and verify the current session through explicit proxies
After handling the confirmed stale process, start the core with the current v2rayN configuration and verify that the expected new PID owns the local listener. Make real HTTPS requests through both the local HTTP and SOCKS entry points and confirm that the active connections correspond to the selected node. Only when both real requests succeed can you say that the current session's explicit proxy paths work.
The system proxy is off in this branch, so do not claim that a browser or device-wide automatic proxy recovered just because an explicit request succeeded. If the browser also needs a system proxy, configure and verify that separately in the same user context.
Version scope and unverified conditions
With Windows 11, v2rayN 7.25.4, Xray 26.9.9, and TUN off, handle a process by exact PID only when its path, start time, parent and listener ownership consistently identify it as stale. If explicit HTTP and SOCKS requests then pass, that confirms only those proxy paths in the current session; investigate the process origin and former endpoint failure separately.
These checks do not verify TUN, automatic startup or persistence after reboot. If the issue returns after sign-in or reboot, collect the parent-child process relationship and listener PID again; a current-session result does not prove a persistent repair.
Sources
Frequently Asked Questions
Why does v2rayN show a new node while requests still use the old one?
Check which PID owns the local listener, along with its parent, start time, and configuration source.
Can I end every Xray process?
No. Handle only an exact old PID after backup and confirmation that it owns the listener and is not part of the active client.
If the system proxy is off and an explicit SOCKS request works, is the browser fixed too?
No. An explicit request and the browser's system proxy are separate paths.
Does recovery in the current session prove the issue will stay fixed after reboot?
No. TUN, automatic startup, and cross-restart behavior were not tested.