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
- When TUN is off and the local proxy works but the browser connects directly, compare the current user's ProxyEnable and ProxyServer values with the client process owner.
- HKCU refers to the account running the query. If another account started the client, its proxy setting may differ from the one read by the browser.
- Set the system proxy under the same account as the browser only when the account context differs or that user's proxy is off and the local proxy works.
- A service or startup task may run under a different account. If the client startup entry’s actual account cannot be confirmed, keep it unknown. Administrator privilege alone does not prove that the account differs; check the process owner before changing how the client starts.
Confirm the failure branch and TUN state
If the v2rayN core is running on Windows and a local proxy request succeeds while a browser using the system proxy connects directly, first confirm that TUN is off. With TUN enabled, traffic follows a different mechanism, so system proxy account scope may not be the only explanation. Also confirm that the browser is actually configured to use the Windows system proxy; some apps keep separate proxy settings.
The observable branch is that the current browser user's system proxy is disabled, or that the client and browser run under different users. A system proxy switch showing “on” still does not prove that real page traffic uses the local proxy. Check the account, active port, and actual browser request next.
Read the current user's proxy state and process owners
Run read-only queries in the same Windows sign-in session as the browser. Inspect that user's HKCU ProxyEnable and ProxyServer values, then compare the owners of v2rayN, its core, and the browser. HKCU is the configuration hive for the account running the command; a terminal started under a different administrator account may read a different user's settings.
The PowerShell commands below display process account names and system proxy values. Account names, process paths, and ports are local information; do not publish the full output. If permissions prevent reading a process owner, leave it unknown instead of escalating access just to inspect it.
Check the current user's system proxy and related process accounts
powershellGet-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings' -Name ProxyEnable,ProxyServer -ErrorAction SilentlyContinue
Get-CimInstance Win32_Process | Where-Object { $_.Name -match 'v2rayN|xray|sing-box|msedge|chrome|firefox' } | ForEach-Object { $owner = Invoke-CimMethod -InputObject $_ -MethodName GetOwner -ErrorAction SilentlyContinue; if ($owner.ReturnValue -eq 0) { [pscustomobject]@{ Process=$_.Name; ProcessId=$_.ProcessId; Domain=$owner.Domain; User=$owner.User } } }
Determine whether the user contexts differ
Compare the browser process account, the v2rayN process account, and the account that ran the query. If the browser follows Windows system proxy settings and its user's HKCU shows ProxyEnable as 0, while the client runs under another account or was started by another user, the proxy may have been written to a different user's settings. If the client and browser accounts match and the proxy is enabled, do not keep assuming that account scope is the cause.
A service, scheduled task, or launch option that uses alternate credentials may run as a different user. If the startup entry’s actual account cannot be read, keep its identity unknown; administrator privilege alone does not prove that the user changed. Read the actual process owner before changing startup behavior.
Set the proxy under the same account only when conditions match
Use v2rayN's system proxy setting in the same account as the browser only when TUN is off, an explicit local proxy request succeeds, the browser follows system proxy settings, and that user's system proxy is actually disabled or the client runs as another user. Confirm that the HTTP, HTTPS, and SOCKS listener ports match the current client settings. Do not enter a guessed port manually.
If the device is managed by an organization or proxy settings are controlled by policy, do not bypass that policy by editing the registry. Record the current user's ProxyEnable and ProxyServer first. An existing proxy may be required by a VPN, business network, or another tool; do not overwrite it and guess what it used to be.
Verify real browser traffic and startup behavior
After the change, read ProxyEnable and ProxyServer again in the same user session and confirm they point to the current v2rayN listener. Then visit an HTTPS site in the target browser and check whether the client shows a connection corresponding to that request. If only the client switch is on or the process exists while the real page still connects directly, continue with the browser's proxy mode and local listener instead of declaring recovery.
If the issue returns only after sign-in or reboot, check which account the client startup entry uses. Under controlled conditions, reboot and recheck the process owner, HKCU values, and real page request. The startup branch is verified on that device only when the actual request succeeds after restart.
Rollback and safety limits
If the change does not help or replaced an existing network proxy, turn off v2rayN's system proxy in the same user context or restore the values recorded before the change. Do not clear proxy settings for every account. System proxy and startup changes persist across sign-in, so back up relevant settings and define the rollback scope first.
If the real HTTPS request succeeds after v2rayN’s system proxy is enabled under the browser’s account, that supports the account-specific path for that setup. It does not establish that elevation caused the problem or that every system proxy issue is an account-permission issue. If the startup entry’s actual account cannot be identified, keep it unknown and account for differences in Windows versions, browser proxy modes, and organization policy.
Sources
Frequently Asked Questions
Why does the browser connect directly when v2rayN says the system proxy is on?
Check the browser user's HKCU proxy values, the client process owner, and whether the browser follows Windows system proxy settings.
Does running as administrator always write settings for another user?
No. Elevation does not necessarily change the account. Read the actual process owner and current HKCU context.
Can I edit ProxyEnable in the registry directly?
Only after confirming the account, the purpose of existing proxy settings, and the rollback value. Prefer the client setting; follow the administrator's policy on managed devices.
If the proxy works after startup, must I test after reboot?
If automatic startup is part of the setup, recheck the account, proxy state, and real browser request through the same user's reboot flow.