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
- If local explicit HTTP and SOCKS requests work, another browser and Chrome Guest mode work, but one profile connects directly, focus on that profile.
- Check macOS system proxy state first, then inspect chrome://extensions and chrome://policy in the affected profile.
- A proxy extension is one possible source of interception. Attribute the issue to it or its setting only after changing one setting in the same profile restores access.
- A separate test profile or Guest mode is a temporary alternative, not proof that the original profile is repaired. The extension change still needs its own verification.
Separate a single Chrome profile issue from a device-wide proxy failure
If explicit requests through local HTTP and SOCKS proxies complete on a Mac, other browsers work, but one Chrome profile connects directly or cannot open sites, focus first on that profile. A second Chrome profile or Guest mode working helps distinguish a browser-profile path from the local proxy listener. It does not show that a Google account is restricted or prove that an extension caused the problem.
System proxy enabled, proxy process running, and a specific browser profile using the proxy are three separate facts. Do not label the client crashed because its window was obscured, a user switched profiles, or a diagnostic page showed a different region.
Check the system proxy and local proxy listener first
Read HTTP, HTTPS, and SOCKS system proxy state for the active network service, and confirm the current local listener ports in v2rayN. From a terminal, make explicit HTTP and SOCKS requests to the same HTTPS test page and record only whether each request completed and its status code. An explicit request does not mean that Chrome used the same proxy settings.
The command below uses port placeholders so the local configuration is not copied into a public page. Do not show the egress IP or share a local user name, actual port, or proxy credentials.
Check request status through local HTTP and SOCKS listeners
shellHTTP_PORT='REPLACE_WITH_CURRENT_HTTP_PORT'
SOCKS_PORT='REPLACE_WITH_CURRENT_SOCKS_PORT'
for mode in http socks5h; do
port="$HTTP_PORT"
[ "$mode" = socks5h ] && port="$SOCKS_PORT"
curl -q --noproxy '' --proxy "${mode}://127.0.0.1:${port}" --connect-timeout 5 --max-time 12 --output /dev/null --write-out "${mode} HTTP %{http_code}\n" https://www.cloudflare.com/cdn-cgi/trace
done
Compare browser behavior in the affected profile
Keep the same Wi-Fi and approximate time. Open the same test page in the original Chrome profile, then compare it with a second profile and Guest mode. Check the page's main request, not only a WebRTC diagnostic field. If the affected profile's main request goes direct while other profiles use the expected proxy egress, investigate that profile's proxy settings, extensions, or policies.
A test that launches Chrome with both a separate user directory and a proxy startup argument changes two things at once, so it cannot prove by itself that an extension is responsible. A working alternative profile shows only that another browsing path is available; verification must return to the original profile.
Inspect profile extensions and browser policies
Switch to the affected Chrome profile, open chrome://extensions, and record the enabled state and proxy mode of proxy or VPN extensions. Then check chrome://policy for applicable proxy policies. Do not infer that an account is restricted because profiles or sync accounts differ. A policy page without a displayed proxy value does not rule out extensions or every other source of overrides.
If an extension offers a “use system proxy” mode, first check whether it is set to direct, manual proxy, or another rule. Record the original switch and mode. Do not disable several extensions at once or reset the entire Chrome profile.
Test the extension hypothesis with one change
Only if the original profile continues to fail, explicit local proxy requests and other profiles work, and a proxy extension could be overriding system settings, record and change that extension's proxy mode in the original profile or temporarily turn off that one extension. If the device is managed by an organization or a policy controls the setting, follow that policy instead of bypassing it.
Keep v2rayN, node, network, and Chrome profile unchanged. Reopen the same HTTPS page and check its main request. If the original profile recovers and its egress matches the explicit proxy request, the evidence narrows the cause to that extension or setting. If nothing changes, restore its previous state and check for other interception sources in that profile.
Verify the real page and restore the original setting if needed
Consider the original profile verified only when its own real page request succeeds, the main request matches the expected proxy egress, and the intended business site also loads. Do not substitute Guest mode, a second profile, or a temporary startup window. Keep a diagnostic page's region label separate from the actual request result.
If the extension change has no effect or breaks access to other sites, restore the switch and proxy mode recorded before the test. Do not clear bookmarks, passwords, history, or the whole profile. If no result was returned after disabling the extension, keep that step marked as pending verification.
Sources
Frequently Asked Questions
Why does one Chrome profile bypass the proxy while other browsers work?
Profiles can have different extensions, proxy modes, or policies. Inspect those settings in the affected profile.
Does Guest mode working prove the extension is the cause?
No. Guest mode differs from the original profile. Change one extension setting in the original profile and retest.
Can I reset Chrome if the system proxy looks right?
Avoid that as a first step. Check the affected profile's extensions and policies; resetting the profile can affect bookmarks, passwords, and local data.
When can I say the issue was fixed after disabling an extension?
The original profile's real page request must succeed and match the expected proxy egress. Until it is retested, keep the result pending.