PuppyIP Resource Center
Network & Connection Troubleshooting 7 min Published 2026-11-17

macOS Apps Bypass v2rayN? Check the System Proxy

With TUN off, an app reaches v2rayN only if it uses an enabled system proxy or connects to a local proxy port itself.

macOS proxy v2rayN system proxy Safari TUN

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

  • A working local HTTP or SOCKS proxy does not mean Safari or another app is sending requests to it.
  • Check the active network service's HTTP, HTTPS, and SOCKS proxy states, then compare an explicit proxy request with a normal app request.
  • Consider enabling the system proxy only when TUN is off, the core is running, an explicit local request succeeds, and the relevant system proxy settings are disabled.
  • Enabling a system proxy affects apps that follow macOS settings across the device. Apps that ignore those settings and some UDP traffic may take another path.

Separate a core problem from a local listener or system proxy problem

If macOS v2rayN has started Xray, TUN is off, and an explicit request through a local HTTP or SOCKS port succeeds while Safari still connects directly, focus on the system proxy settings. With TUN off, an app generally needs to read macOS proxy settings or be configured to use a local proxy itself. A running core does not automatically redirect every app's connection.

This is different from an unreachable node. A successful local proxy request shows that the tested port, active configuration, and destination worked for that one request; it does not verify Safari. If the client interface and macOS state do not explain why automatic proxy configuration failed, keep that cause unknown. Do not guess that a permission, network, or version defect is responsible.

Read the active network service's proxy settings

First identify the network service macOS is currently using. Wi-Fi is common, but a Mac may use Ethernet, a VPN, or a custom service name. These commands only read settings; they do not enable or clear a proxy. If the active service is not named Wi-Fi, replace that name with the one shown in the list. Check web HTTP, secure web HTTPS, and SOCKS separately.

Inspect network services and system proxy states

shell
networksetup -listallnetworkservices
networksetup -getwebproxy "Wi-Fi"
networksetup -getsecurewebproxy "Wi-Fi"
networksetup -getsocksfirewallproxy "Wi-Fi"
Read-only queries. Replace Wi-Fi with the active network service name. Output may include a local proxy address and port; do not post the full output publicly.

Compare an explicit local proxy request with Safari

Read the current HTTP and SOCKS listener ports from v2rayN. Do not copy a port from an old screenshot or another device. Replace both placeholders below with the current listener ports, then make an HTTPS request through each proxy type. With an explicit proxy, curl checks whether that protocol entry completed this request. It does not show that Safari has read the system settings or that every site or UDP app will work.

Then open the same HTTPS test endpoint in Safari. If both explicit requests work but Safari still connects directly, record “local proxy works” and “system proxy is disabled or unapplied” as separate observations. If an explicit request also fails, check the listener port, active configuration, and core logs before changing a device-wide proxy setting.

Test the local HTTP and SOCKS listeners separately

shell
HTTP_PORT='REPLACE_WITH_CURRENT_HTTP_PORT'
SOCKS_PORT='REPLACE_WITH_CURRENT_SOCKS_PORT'
curl --silent --show-error --max-time 15 --proxy "http://127.0.0.1:${HTTP_PORT}" --output /dev/null --write-out 'HTTP %{http_code}\n' https://www.cloudflare.com/cdn-cgi/trace
curl --silent --show-error --max-time 15 --proxy "socks5h://127.0.0.1:${SOCKS_PORT}" --output /dev/null --write-out 'HTTP %{http_code}\n' https://www.cloudflare.com/cdn-cgi/trace
Replace the placeholders with the current client ports first. These commands make real HTTPS requests; success only confirms that each explicit proxy entry completed that request.

Enable the system proxy only when the evidence matches

Use the client's “Set system proxy” action only when TUN is off, Xray or the active core is still running, at least one explicit local proxy request succeeds, and the active network service shows the relevant system proxies are disabled. Confirm that the HTTP, HTTPS, or SOCKS listener selected by v2rayN matches the port checked above. Do not guess a port or overwrite settings used by another VPN, company proxy, or network tool.

A system proxy is a device-level setting. It changes the route used by other apps that follow macOS system proxy settings. If the Mac is managed by an organization, or another proxy belongs to a separate network tool, preserve its settings and confirm the scope before switching. TUN and system proxy are different forwarding modes; do not layer both modes without a clear reason just to work around this symptom.

Verify with the real app and the system state

After enabling the setting, repeat the read-only queries and check that the active network service shows the expected proxy type and local port. Reopen the test page in Safari, then try an HTTPS site that normally fails. Check whether the real page request completes and whether v2rayN shows a connection associated with that request. An enabled switch alone does not prove that app traffic used the proxy.

If Safari recovers but another app still connects directly, first check whether that app follows macOS system proxy settings. If macOS still reports the proxy as disabled, the port does not match, or Safari reports an error, continue with the service name, proxy protocol, and local listener instead of attributing the result to the node or DNS.

Rollback scope and diagnostic limits

To undo this change, turn off the system proxy in v2rayN, or disable only the HTTP, HTTPS, and SOCKS proxy states enabled for this change in Network Settings. Use the read-only commands above to confirm the resulting state. Do not clear proxy settings for other network services or remove a VPN, certificate, or configuration profile as a substitute for rollback.

This guide covers the diagnostic branch where TUN is off, an explicit local proxy works, and a normal app does not use the system proxy. The evidence does not identify why automatic proxy setup failed, and behavior is not guaranteed to match across every macOS release, network service, or app that ignores system proxy settings. Test results, switch state, and real application traffic are separate evidence and should be recorded separately.

Sources

Frequently Asked Questions

Why does Safari connect directly while the core is running?

With TUN off, the core does not automatically take over every app. Safari needs an enabled macOS system proxy or its own proxy configuration.

Does a successful explicit SOCKS request prove that the system proxy works?

No. The explicit request only checks the selected local SOCKS entry. Check the macOS settings and test Safari separately.

Does enabling the system proxy affect the whole Mac?

It affects apps that follow the system proxy settings for that network service. Managed settings, VPNs, apps that ignore system proxies, and some UDP traffic may behave differently.

Should I change permissions if automatic system proxy setup fails?

The reason automatic setup failed is unknown. Check TUN state, an explicit local request, and system proxy state first; do not change permissions based on a guess.