[Bug] Incompatibility with Shifter.io Residential Proxies (WebRTC/Gateway Leak & Mislocation)

[pducthang]

Issue Description:
I am currently using a CloakBrowser Pro Plan. However, when using Shifter.io Residential Proxies, the browser fails to fully mask the proxy's underlying entry gateway, resulting in fingerprint inconsistency, location spoofing failure, and account bans on Google services.

In contrast, Webshare Proxies (Direct Exit / 1-1) work flawlessly under the exact same browser configuration and profile settings.

Steps to Reproduce:
Configure Profile A with a Shifter.io Residential Proxy targeted to South Korea (e.g., p.shifter.io:443).
Configure Profile B with a Webshare Proxy (e.g., p.webshare.io:80).
Launch both profiles and test against Google Maps and Pixelscan.

Expected Behavior:
Both proxy providers should route traffic cleanly to South Korea.
WebRTC, DNS, GeoIP, and TCP sockets should be fully synchronized.
Pixelscan should mark the fingerprint as consistent and legitimate.

Actual Behavior:
With Webshare Proxy:
Google Maps: Accurately detects location in South Korea.
Pixelscan: Passes all checks smoothly with 0 leaks.
Network Layer: Socket IP matches the exit IP directly (1-1 Direct Exit).

With Shifter.io Proxy:
Google Maps: Misidentifies location based on the entry gateway instead of the exit IP.
Pixelscan: Flags the environment and exposes an active intermediary gateway in Singapore (143.198.216.110).
Result: Accounts get flagged/banned due to network-layer mismatch.

Root Cause Analysis (Technical Log):
Inspecting the network layer via curl -v reveals that Shifter uses a multi-hop HTTP CONNECT tunnel carrying an extra transit header (X-Proxy-Exit-Ip):
Plaintext

• Trying 143.198.216.110:443... (DigitalOcean Singapore Gateway)
• CONNECT tunnel: HTTP/1.1 negotiated
  < X-Proxy-Exit-Ip: 218.235.86.9 (South Korea Exit IP)
  ...
  {
  "origin": "218.235.86.9"
  }
  Webshare connects directly to the destination socket, whereas Shifter routes through a Singapore entry gateway first. The browser core currently fails to pre-resolve and synchronize the C++ network stack before rendering, leaving the Singapore entry gateway exposed to target sites.

Environment:
OS: Windows 11 / macOS
Proxy Providers Tested: Shifter.io (Fails) vs Webshare.io (Passes)
Target Country: South Korea (KR)

[Cloak-HQ]

Thanks for the report, the curl -v trace is useful.

We don't have a Shifter account, so we can't reproduce this here. What we can do is read what your setup resolves.

Could you send the output of cloakbrowser info --proxy <url> for both proxies, the Shifter one and the Webshare one? It resolves for real and prints the exit IP plus the timezone and locale a launch would apply, so the two side by side show whether they diverge before the browser even starts.

A full-page Pixelscan screenshot at failure would help too.

With those we can tell you whether the divergence is on our side or in Shifter's routing, and fix it if it's ours.

[pducthang]

Thanks for the feedback. Here are the requested details:

Shifter Residential Proxies	Webshare Residential Proxies
CloakBrowser diagnostics	CloakBrowser diagnostics
Wrapper: 0.5.7	Wrapper: 0.5.7
Python: 3.11.4	Python: 3.11.4
OS: Windows AMD64	OS: Windows AMD64
Platform: windows-x64	Platform: windows-x64
Channel: Stable	Channel: Stable
Version: 146.0.7680.177.5 (free)	Version: 146.0.7680.177.5 (free)
Binary: C:\Users\XXX.cloakbrowser\chromium-146.0.7680.177.5\chrome.exe	Binary: C:\Users\XXX.cloakbrowser\chromium-146.0.7680.177.5\chrome.exe
Installed: False	Installed: False
Cache: C:\Users\XXX.cloakbrowser\chromium-146.0.7680.177.5	Cache: C:\Users\XXX.cloakbrowser\chromium-146.0.7680.177.5
Launch: binary not installed	Launch: binary not installed
License: Free (no key)	License: Free (no key)
GeoIP DB: present	GeoIP DB: present
Exit IP: 220.123.238.146	Exit IP: 1.226.241.171
Timezone: Asia/Seoul	Timezone: Asia/Seoul
Locale: ko-KR	Locale: ko-KR
Modules: • playwright: ok • geoip2: ok • aiohttp: ok • websockets: ok	Modules: • playwright: ok • geoip2: ok • aiohttp: ok • websockets: ok

1: shifter_whoernet.png
2: shifter_pixelscan.png
3: shifter_browserleaks.png
4: shifter_google_map.png

[Cloak-HQ]

Thanks, the screenshots answered it.

Shifter is rotating the exit per connection. In that one session BrowserLeaks saw a Korean exit while Pixelscan and Whoer saw a Singapore one (103.106.229.138, BrainStorm Network). Your info output resolved 220.123.238.146 in Korea.

We resolve the exit IP once at launch and use it for timezone, locale, and the WebRTC IP. With a rotating exit that value goes stale immediately, so the page claims Korea while the request arrives from Singapore. Pixelscan shows both: IP 103.106.229.138, WebRTC IP 220.123.238.146. That mismatch is the signal, not a leaked gateway.

Webshare works because it's 1-to-1, so what we resolve at launch is what the site sees.

Use a Shifter sticky session so the exit stays fixed for the life of the browser. That should bring both into line.