Request: More and better Proxy settings

[INeatFreak]

When using Proxy, all apps by default set to use it. Which is annoying since I only want to use for few apps, so had to go one by one every app and set to bypass proxy for each one. Also you might accidentally leak your Proxy IP to new apps when you forgot to check "Bypass from all proxies" toggle, or your account could get banned in some sensitive apps for using VPN.

A better solution would be to have one Global Proxy toggle in settings that applies the proxy by default, but while disabled only apps set to use proxy will use it. As addition if possible I would like an option to use multiple proxies, to choose which app uses which. As example an ideal solution would look like this:

@GlobalSettings

Select Default Proxy [ None, Proxy1, Proxy2 ]

@PerAppSettings / Reddit

Select Proxy [ Default, Bypass, Proxy1, Proxy2 ]

• Default - Default proxy selected (if any) in global settings
• Bypass - ignores all proxies for this app
• Proxy1 - uses proxy1
• Proxy2 - uses proxy2 and so on..

[ignoramous]

I am not sure what you're asking for and so I've moved it to discussions as most of the features being requested (if not all), already exist. At any rate, if you think I am mistaken, let me know, and I'll create a new issue for your specific use cases (if they're not covered already, as detailed below). Thanks for your feedback, appreciate it. (:

---

Default - Default proxy selected (if any) in global settings

In Advanced mode WireGuard, turning on Always-on makes it the "Default proxy" (as in your usecase).

Bypass - ignores all proxies for this app

This setting, as you already seem to know, does exist per-app; settable from Configure -> Apps -> (specific app) -> Bypass app from proxies.

Proxy1 - uses proxy1 / Proxy2 - uses proxy2 and so on..

Already possible with Advanced mode WireGuard. Tap on Configure -> Proxy -> Setup WireGuard -> (Advanced) -> (specific WireGuard) -> Apps button.

A better solution would be to have one Global Proxy toggle in settings that applies the proxy by default,

That's Simple mode WireGuard.

Also you might accidentally leak your Proxy IP to new apps when you forgot to check "Bypass from all proxies" toggle

Hm, most folks have Configure -> Firewall -> Universal firewall rules -> Block newly installed apps turned on; which in fact, blocks all outgoing traffic of newly installed third-party apps. You could consider using it if you're worried about Proxy IP leaking to untrusted apps.

[INeatFreak]

I don't use WireGuard, that's not sufficient anymore in today's age unfortunately. it's protocol is easily recognizable by DPI (Deep Packet Inspection) and gets blocked in a lot of restricted countries. Currently using local proxy v2ray with SOCKS5 and we can only have singular instance. We have basically no filtering for SOCKS5 at all, it applies to all apps. Is there a better way maybe I'm not aware of?

[ignoramous]

Ah gotcha. In that case, please track:

• [Feature request] Per app proxy for socks/http proxy #1126
• Multiple proxy running at the same time  #1623

[INeatFreak]

Is there any updates on XRay and Tailscale implementations? If these two were to be implemented I wouldn't even need more options for SOCKS5, it's a bandaid fix at best since Tailscale app only has VPN not proxy, even if they add proxy support then still I won't be able to use v2ray simultaneously since there's only support for one SOCKS5 connection in this app.

These two are the last missing pieces imo for any privacy focused users.

[ignoramous]

Is there any updates on XRay and Tailscale implementations?

Hi: No updates, unfortunately. We're mostly trying to stabilize the app, retouch the UI right now.

I expect Tailscale and XRay to happen sometime in the coming months. Though, no guarantees. The reason is: It has been 2yrs+ and we're still fixing and implementing newer features in WireGuard. Adding XRay and Tailscale to the mix will complicate things further. That is, implementing the first cut for both XRay and Tailscale is likely "easier" than supporting the usecases / bugs that will follow after. We simply do not have the bandwidth to do so, currently.