Skip to content

Support Running Windscribe as a Local Proxy (VPN-over-VPN) #293

@SinaKarimi7

Description

@SinaKarimi7

Is your feature request related to a problem? Please describe.

Windscribe already supports routing traffic through an externally exposed proxy (host:port), which is useful in some scenarios. However, many censorship-bypass tools and VPNs (including some regional VPNs or ISP-friendly tunnels) do not expose a proxy interface at all — they only provide system-level tunneling.

In heavily restricted countries (for example Iran), Windscribe is usually my first choice. But when direct access to Windscribe is blocked or unstable, users are forced to temporarily rely on other tools (local VPNs, Cloudflare WARP, Zero Trust, etc.) just to regain basic connectivity. These tools often keep the local country IP and cannot be used as upstream proxies.

Because Windscribe currently works mainly in TUN (system-wide routing) mode and does not expose a local proxy endpoint, it becomes impossible to run Windscribe behind these tools (VPN-over-VPN).

Describe the solution you'd like

Add support for running Windscribe as a local proxy (SOCKS5 and/or HTTP) in addition to the existing TUN mode.

This would allow:

  • Windscribe to be used behind another VPN or tunnel (VPN-over-VPN)
  • Chaining Windscribe on top of tools like Cloudflare WARP, Zero Trust, or regional VPNs that do not expose proxies
  • Selective or per-application routing using proxy-aware apps
  • Keeping Windscribe as the primary exit node even when initial connectivity requires another tunnel

This could be implemented as:

  • A selectable mode (TUN mode vs Local Proxy mode)
  • Or an advanced option to expose a local proxy on 127.0.0.1 or 0.0.0.0

Describe alternatives you've considered

  • Using Windscribe’s existing outbound proxy support (not applicable when the upstream tool has no proxy interface)
  • Switching entirely to other VPN tools when Windscribe is blocked
  • Complex OS-level routing or packet filtering rules

These approaches are either unreliable, overly complex, or defeat the purpose of using Windscribe as the main VPN.

Additional context

In high-censorship environments, VPN-over-VPN and chaining techniques are not edge cases — they are often required for basic access. Exposing Windscribe as a local proxy would greatly improve reliability, flexibility, and real-world usability in these regions while complementing (not replacing) the existing TUN-based design.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions