For anyone installing v2rayN on a Mac for the first time or troubleshooting a proxy that stopped working after a system upgrade. Start by identifying whether the issue is app launch, local listening, or system proxy configuration, then follow the relevant steps. Only consider allowing the app individually if its source is known and macOS offers an exception.
First, distinguish a launch block from a proxy issue
Gatekeeper checks apps downloaded from the internet, using signing and notarization as part of its assessment. “Unable to Verify Developer” means macOS could not verify this copy under its default policy; it does not mean network access was denied, nor does it prove the file is safe. If the app’s source is unknown, macOS reports malware, or you see an “app is damaged” warning, do not treat a standard developer-verification exception as a fix.
Start with where the warning appears
RecommendedIf double-clicking the app does not open a main window, address the launch warning first. If the main window appears but your connection drops only after enabling the proxy, check the core logs and proxy settings for the active network service. Note the exact warning, then change one setting at a time.
Best for: first-time installs or unclear issues after an upgrade
Test the connection without a proxy
If v2rayN opens, note your existing proxy settings, then clear any settings changed during this test and use the same browser to revisit a site that normally works without a proxy. If direct access also fails, check Wi-Fi, captive portal sign-in, or network policies first; do not keep changing node settings.
Best for: webpages stop loading after switching networks
Bottom line: check whether the main window opens
If the main window opens, leave your current security settings as they are and check the core logs instead. Being allowed to launch does not mean the bundled core is running successfully.
Allow the app individually in Privacy & Security
Check the installer
Confirm the download came from a trusted release source. Choose Apple menu → “About This Mac” to see whether your Mac has Apple silicon or an Intel processor, then select the matching arm64 or x64 build. After extracting it, use Finder to make sure you keep opening the same copy of the app; avoid testing separate copies in Downloads and Applications.
Read the warning
Double-click the app and read the macOS warning. If it only says the developer cannot be verified and you know the app’s source, close the warning and continue to the next step. If macOS says the app will damage your computer, or you cannot verify its source, do not open it; check with the publisher or your device administrator.
Open Security settings
On macOS 13 and later, go to Apple menu → “System Settings” → “Privacy & Security” and scroll down to “Security.” Find the entry for the app that was just blocked. Click “Open Anyway” only after confirming it matches the copy you just tried to open.
Confirm this authorization
Confirm the macOS dialog and authenticate with an authorized account if prompted. If the button does not appear, try opening the same app again, then immediately return to Settings and check. If your device is managed by a school or company, ask the administrator whether exceptions are allowed; do not disable system-wide protections.
Check the core logs
Once the main window opens, select an existing configuration and check the client logs to confirm the corresponding core starts and the local listener has no errors. Do not enable TUN or bulk-update subscriptions yet; keep app launch, core startup, and remote connectivity separate while troubleshooting.
Check system proxy settings and local network access
System proxy settings belong to a network service. v2rayN sets an address and port for apps that follow the system proxy; this is not a system-wide internet access permission for every app. On Wi-Fi, choose “Set system proxy” from the client’s “System Proxy” menu. If your client has a different interface, use its current system proxy option. Then go to Apple menu → “System Settings” → “Network” → “Wi-Fi” → “Details” for the connected network → “Proxies” to check the settings. For a wired connection, check the Ethernet service in use.
- Check the listening port: In v2rayN, go to “Settings” → “Parameter Settings” to check the local listening port, then compare it with the core logs. If the port is
10808, runlsof -nP -iTCP:10808 -sTCP:LISTENin Terminal to see which process is listening. If another process is using the port, identify it before closing a known conflicting app or changing the port, then reapply the system proxy. - Match the proxy type: “Web Proxy (HTTP),” “Secure Web Proxy (HTTPS),” and “SOCKS Proxy” are separate settings. Use the setting and listener type that the client actually configured; do not enter a SOCKS-only port under HTTP. If you previously used automatic proxy configuration or a workplace proxy, note its original value so you can restore it.
- Grant only the access needed: Starting with macOS 15, the system may require local network permission to access devices on your local network. If you need to access a local network address, go to “System Settings” → “Privacy & Security” → “Local Network” and check for the app that matches the access request. Using a local proxy through
127.0.0.1usually does not require local network access.
Restore proxy settings after a system upgrade
- Confirm which copy of the app is running. Open the copy you plan to keep using from Applications. If you switched app bundles after upgrading and see the verification warning again, treat it as a new launch check and verify the source again. Do not assume an exception for the old copy also applies to the new one.
- Get the core listening again first. Check the client logs to confirm startup. If the port is in use, resolve the listener conflict first. If the logs show a missing or unexecutable core file, check that the archive was fully extracted and that you have not mixed files for different architectures. If the core is not listening, repeatedly enabling the system proxy will only point apps to an unavailable port.
- Reapply settings to the active network. Once the core is ready, use the client’s “System Proxy” menu to clear the old values it set, then configure the proxy again automatically. Check the result under “Proxies” for the active network service. If macOS asks for authentication, confirm only when you initiated the action and the prompt matches what you are doing. Have an administrator handle managed settings.
- Test the browser and other apps separately. Compare with a browser that follows the system proxy, then test the app you are troubleshooting. If the browser works but the target app does not, check whether that app uses its own proxy settings. If the browser also fails, use the core logs to distinguish a refused local connection from a remote connection timeout; avoid repeatedly changing system permissions.
Common questions about first launch and network access
Why can’t I find “Open Anyway”?
Open the copy you plan to use from Finder, note the exact warning, then check near the bottom of “Privacy & Security.” If macOS warns that the app is damaged or contains malware, or your device policy does not allow exceptions, this option does not apply.
Why can’t I access websites after quitting v2rayN?
Check whether the active network service is still sending requests to a local port that is no longer listening. Reopen the client and use its “System Proxy” menu to clear the settings it added. If you had a workplace proxy or automatic configuration address before, restore the value you noted instead of turning off every proxy setting.
v2rayN isn’t listed under Local Network. Should I add it manually?
First check whether the destination is a device on your local network. If a remote server is unreachable, check its address and port and review the core logs first. If you do need local network access, retry the action and check whether macOS prompts for permission; you do not need extra authorization for ordinary internet access.