GithubHelp home page GithubHelp logo

wiresock / proxifyre Goto Github PK

View Code? Open in Web Editor NEW
183.0 10.0 14.0 204 KB

ProxiFyre: SOCKS5 Proxifier for Windows

Home Page: https://www.ntkernel.com

License: GNU Affero General Public License v3.0

C# 1.29% C 6.79% C++ 91.54% PowerShell 0.38%
proxifier socks5 windows proxifier-alternative

proxifyre's Introduction

ProxiFyre: SOCKS5 Proxifier for Windows

ProxiFyre elevates the foundational capabilities of the Windows Packet Filter's socksify demo, introducing robust enhancements. Not only does it seamlessly integrate support for UDP, but it also empowers users with the flexibility of managing multiple proxy instances. Streamlining its configuration process, ProxiFyre now dynamically sources its settings from an app-config.json file, ensuring a more intuitive and user-friendly experience. Furthermore, with its adaptability in mind, ProxiFyre can be effortlessly configured to run as a Windows Service, providing continuous operation without the need for manual intervention.

Configuration

The application uses a configuration file named app-config.json. This JSON file should contain configurations for different applications. Each configuration object should have the following properties:

  • appNames: An array of strings representing the names of applications this configuration applies to.
  • socks5ProxyEndpoint: A string that specifies the SOCKS5 proxy endpoint.
  • username: A string that specifies the username for the proxy.
  • password: A string that specifies the password for the proxy.
  • supportedProtocols: An array of strings specifying the supported protocols (e.g., "TCP", "UDP").

LogLevel

LogLevel can have one of the following values which define the detail of the log: None, Info, Deb, All

appNames

On the application name, it can be a partial name or full name of the executable, e.g. firefox or firefox.exe both will work for the firefox browser, but also any application whose name includes firefox or firefox.exe, e.g. NewFirefox.exe. If the pattern specified in the appName contains slashes or backslashes then it is treated as a pathname and instead of matching the executable name, the full pathname is matched against the pattern. It allows specifying an entire folder using a full or partial path which can be convenient for UWP applications, e.g. C:\\Program Files\\WindowsApps\\ROBLOXCORPORATION.ROBLOX for ROBLOX.

SOCKS5 Proxy Authorization

If the SOCKS5 proxy does not support authorization, you can skip the username and password in the configuration.

Here is an example configuration:

{
 "logLevel": "None",
 "proxies": [
         {
         "appNames": ["chrome", "C:\\Program Files\\WindowsApps\\ROBLOXCORPORATION.ROBLOX"],
         "socks5ProxyEndpoint": "158.101.205.51:1080",
         "username": "username1",
         "password": "password1",
         "supportedProtocols": ["TCP", "UDP"]
         },
         {
         "appNames": ["firefox", "firefox_dev"],
         "socks5ProxyEndpoint": "127.0.0.1:8080",
         "supportedProtocols": ["TCP"]
         }
     ]
}

Quick Start Guide

This guide provides step-by-step instructions on how to set up and run the ProxiFyre application.

Pre-installation Steps

1. Install Windows Packet Filter (WinpkFilter)

Windows Packet Filter is a critical dependency for our project.

2. Install Visual Studio Runtime Libraries

Visual Studio Runtime Libraries are required for running applications developed with Visual Studio.

  • Go to Visual Studio 2022 redistributable download page
  • Identify your system architecture (x64, x86, or ARM64).
  • Download the appropriate installer for your platform to ensure compatibility and optimal performance.
    • For x64 systems, download the x64 installer.
    • For x86 systems, download the x86 installer.
    • For ARM64 systems, download the ARM64 installer.
  • Locate the downloaded installer and double-click on it to begin the installation.
  • Follow the on-screen instructions to complete the installation

Please ensure you download the correct installer to avoid any installation issues.

Installation Steps

  1. Download the Latest Release: Visit our GitHub page to download the latest release of the ProxiFyre software.

  2. Unzip the Software: After downloading, extract the contents of the .zip file to your preferred location.

  3. Create app-config.json File: Following the template provided in the Configuration section of this document, create an app-config.json file. This file is crucial for the software to function properly. Save this file in the main application folder.

Running the Application

  1. Run the Application: Navigate to the directory where you extracted the software. Find the main application executable (.exe file) and run it. It's recommended to run the application as an administrator to ensure all functionalities work as expected.

Running as a Service

ProxiFyre can be installed and run as a Windows service. Follow these steps:

  1. Open a command prompt as an administrator.
  2. Navigate to the directory containing ProxiFyre.exe.
  3. Use the following command to install the service:
    ProxiFyre.exe install
    
  4. Start the service with:
    ProxiFyre.exe start
    
  5. To stop the service, use:
    ProxiFyre.exe stop
    
  6. If you wish to uninstall the service, use:
    ProxiFyre.exe uninstall
    

Logging

Logs are saved in the application folder under the /logs directory. The details and verbosity of the logs depend on the configuration set in the app-config.json file.

Build Prerequisites

Before starting the build process, ensure the following requirements are met:

  1. Install vcpkg: You can download and install vcpkg from the official website here.

  2. Install Microsoft GSL library via vcpkg: Once vcpkg is installed, use it to download and install the Microsoft GSL library. Run the following commands in your terminal:

    vcpkg install ms-gsl:x86-windows ms-gsl:x64-windows ms-gsl:arm64-windows
    
  3. Add online NuGet Package Source: In some cases, you may need to add an online NuGet Package Source. To do this, navigate to Visual Studio->Tools->Options->NuGet Package Manager->Package Sources and add https://nuget.org/api/v2.

Projects

This repository consists of three main projects:

1. ndisapi.lib

This is an adopted Windows Packet Filter NDISAPI static library project.

2. socksify

This project is a .Net C++/CLI class library that implements the local SOCKS5 router functionality.

3. ProxiFyre

This is a .Net-based Windows console application that employs the functionality provided by the socksify .Net C++/CLI class library.

proxifyre's People

Contributors

wiresock avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

proxifyre's Issues

Thanks

Thanks for the binaries

Enable/Disable proxy for a specific program

Hello, first of all, thanks for providing a working proxyfire in c#. I have some questions as I want to use the project in my own program.

Any way to control several proxies for different programs with the ability to enable/disable proxies for a particular program without restarting the whole service?

App is still writing logs even though the log level is set to 'None' in app-config.json

This is my app-config.json:

{
  "logLevel": "None",
  "proxies": [
  <Hidden for readability>
  ]
}

But new files keep appearing in the logs directory. For example, one of them contains:

2024-05-16 10:07:10.0908|INFO|ProxiFyre.ProxiFyreService|Successfully associated Skype to censored:1080 SOCKS5 proxy with protocols TCP, UDP!
2024-05-16 10:07:10.1926|INFO|ProxiFyre.ProxiFyreService|ProxiFyre Service is running...

I've restarted ProxyFyre multiple times using the following commands:

net stop ProxiFyreService
net start ProxiFyreService

Can support PID?

Bro, you're amazing. I didn't expect you to go even further. I wonder if you can support not only passing names but also pids? Thank you so much, sincerely!

method selection data may be irregular, incompatible with 3proxy

Hi, thank you for this great software.

I had a problem (connection is reset) in using proxifyre with SOCKS5 server 3proxy (https://3proxy.ru/), and I figured out that the problem lies in method selection.

Even when no password is specified, Proxifyre sends the following method selection data:

05 02 00 02

This means, 05 (SOCKS v5), 02 (two methods are available), 00 (first method: no auth), 02 (second method: password auth)
3proxy seems to prefer password auth than no auth (https://github.com/3proxy/3proxy/blob/29ef226b3cbdc2f1cefd8d6d54387bcd67a38384/src/socks.c#L63) and requests password, resulting in authentication failure and connection being reset.

Proxifyre still works with other SOCKS5 proxy that prefers no auth to password auth, but I guess Proxifyre is responsible for this problem.

Specifically, when no password is specified, Proxifyre should send the following method selection data:

05 01 00

node.exe

Hello!
Thanks for a great tool!
Have one problem -
image
made picrel config, but node still ignores socksify and knocks straight to the server
image

Is there any solutions?

Not working - config and log provided

I am simply testing with Tor and msedge (tor socks is running and listening on 127.0.0.1:9050)

I also tried with a remote socks5 and it never actually connects to it.

Could it be finding the wrong network interface?
Is there any conflict if I'm using wiresock vpn client at the same time? (note that my Wiresock config only has 10.20.1.0/24 in AllowedIPs)

 "logLevel": "All",
 "proxies": [
         {
         "appNames": ["msedge"],
         "socks5ProxyEndpoint": "127.0.0.1:9050",      
         "supportedProtocols": ["TCP"]
         }
     ]
}

`2023-09-15 13:41:17.6108|INFO|ProxiFyre.ProxiFyreService|Successfully associated msedge to 127.0.0.1:9050 SOCKS5 proxy with protocols TCP!
2023-09-15 13:41:17.6637|INFO|ProxiFyre.ProxiFyreService|ProxiFyre Service is running...
2023-09-15 13:41:18.6096|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:17::Message::Creating SOCKS5 Local Router instance...::0
2023-09-15 13:41:18.6096|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:17::Message::SOCKS5 Local Router instance successfully created.::0
2023-09-15 13:41:18.6096|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:17::Message::Local TCP proxy for 127.0.0.1:9050 is listening port: 50824::0
2023-09-15 13:41:18.6096|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:17::Message::socks5_local_router:: Detected default interface {675D97D3-0744-40EF-AD34-BB3227972487}::0
2023-09-15 13:41:18.6096|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:17::Message::SOCKS5 Local Router instance started successfully.::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::Redirecting TCP: 192.168.1.195 : 50827 -> 40.71.99.188 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::NEW TCP: 192.168.1.195 : 50827 -> 40.71.99.188 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::Redirecting TCP: 192.168.1.195 : 50829 -> 52.123.245.98 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::NEW TCP: 192.168.1.195 : 50829 -> 52.123.245.98 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::Redirecting TCP: 192.168.1.195 : 50830 -> 40.71.99.188 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:24::Message::NEW TCP: 192.168.1.195 : 50830 -> 40.71.99.188 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:25::Message::Redirecting TCP: 192.168.1.195 : 50831 -> 52.123.245.98 : 443::0
2023-09-15 13:41:25.6676|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:25::Message::NEW TCP: 192.168.1.195 : 50831 -> 52.123.245.98 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:25::Message::Redirecting TCP: 192.168.1.195 : 50827 -> 40.71.99.188 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:25::Message::Redirecting TCP: 192.168.1.195 : 50829 -> 52.123.245.98 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:25::Message::Redirecting TCP: 192.168.1.195 : 50830 -> 40.71.99.188 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:26::Message::Redirecting TCP: 192.168.1.195 : 50831 -> 52.123.245.98 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:26::Message::Redirecting TCP: 192.168.1.195 : 50834 -> 142.250.74.132 : 443::0
2023-09-15 13:41:26.6796|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:26::Message::NEW TCP: 192.168.1.195 : 50834 -> 142.250.74.132 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50844 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50844 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50845 -> 142.250.74.131 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50845 -> 142.250.74.131 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50846 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50846 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50850 -> 96.16.49.223 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50850 -> 96.16.49.223 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50851 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50851 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50852 -> 142.250.74.131 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50852 -> 142.250.74.131 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50853 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50853 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50854 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50854 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50855 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::NEW TCP: 192.168.1.195 : 50855 -> 204.79.197.239 : 443::0
2023-09-15 13:41:27.6873|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:27::Message::Redirecting TCP: 192.168.1.195 : 50834 -> 142.250.74.132 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50845 -> 142.250.74.131 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50846 -> 204.79.197.239 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50844 -> 204.79.197.239 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50850 -> 96.16.49.223 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50853 -> 204.79.197.239 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50852 -> 142.250.74.131 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50851 -> 204.79.197.239 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50854 -> 204.79.197.239 : 443::0
2023-09-15 13:41:28.6927|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:28::Message::Redirecting TCP: 192.168.1.195 : 50855 -> 204.79.197.239 : 443::0
2023-09-15 13:41:30.7052|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::Redirecting TCP: 192.168.1.195 : 50857 -> 51.195.60.196 : 80::0
2023-09-15 13:41:30.7052|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::NEW TCP: 192.168.1.195 : 50857 -> 51.195.60.196 : 80::0
2023-09-15 13:41:30.7052|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::Redirecting TCP: 192.168.1.195 : 50858 -> 51.195.60.196 : 80::0
2023-09-15 13:41:30.7052|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::NEW TCP: 192.168.1.195 : 50858 -> 51.195.60.196 : 80::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::Redirecting TCP: 192.168.1.195 : 50859 -> 51.195.60.196 : 80::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:30::Message::NEW TCP: 192.168.1.195 : 50859 -> 51.195.60.196 : 80::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50864 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50864 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50865 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50865 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50868 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50868 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50869 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50869 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50870 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50870 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::Redirecting TCP: 192.168.1.195 : 50871 -> 204.79.197.239 : 443::0
2023-09-15 13:41:31.7193|INFO|ProxiFyre.ProxiFyreService|2023-09-15 11:41:31::Message::NEW TCP: 192.168.1.195 : 50871 -> 204.79.197.239 : 443::0```

Fail to launch

Running the exe results in a commandline window flashing for a sec and then closing without launching the program. Here's the log. Tried with admin too, no result.

Configuration Result:
[Success] Name ProxiFyreService
[Success] DisplayName ProxiFyre Service
[Success] Description ProxiFyre - SOCKS5 Proxifier Service
[Success] ServiceName ProxiFyreService
Topshelf v4.3.0.0, .NET Framework 4.8.4515.0 (4.0.30319.42000)
Topshelf.Hosts.ConsoleRunHost Error: 0 : An exception occurred, System.IO.FileNotFoundException: Could not find file 'D:\Users\AR45H\Desktop\ProxiFyre-v1.0.18-x64\app-config.json'.
File name: 'D:\Users\AR45H\Desktop\ProxiFyre-v1.0.18-x64\app-config.json'
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
   at System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost)
   at ProxiFyre.ProxiFyreService.Start()
   at Topshelf.ServiceConfiguratorExtensions.<>c__DisplayClass2_0`1.<WhenStarted>b__0(T service, HostControl control)
   at Topshelf.Builders.DelegateServiceBuilder`1.DelegateServiceHandle.Start(HostControl hostControl)
   at Topshelf.Hosts.ConsoleRunHost.Run()

Configuration hot reload

Cool tool! Thank you

is there a way of editing the config file without having to restart the program?

Cpu utilization

High cpu usage with network traffic, also when no one of whitelisten app is used.
Seems that the filter always monitor all network traffic, and cpu usare spikes high.

Win 8.1

Fyi, after few minutes, using proxifyre on win8.1, the nic connectivity loose ip address and network totally crash.

mstsc (windows remote desktop) Error

ssh tunnel is running and confirmed working.

I have set up proxyfire as such :

"logLevel": "All",
 "proxies": [
         {
         "appNames": ["mstsc","C:\\Windows\\SysWOW64\\mstsc.exe"],
         "socks5ProxyEndpoint": "192.168.0.5:6666",
		 "supportedProtocols": ["TCP", "UDP"]
         }
     ]
}

When I run mstsc directly, it works, but through proxyfire I get the following error:
image

Here are the logs :

2024-02-27 17:54:04.7560|INFO|ProxiFyre.ProxiFyreService|Successfully associated mstsc to 192.168.0.5:6666 SOCKS5 proxy with protocols TCP, UDP!
2024-02-27 17:54:04.7751|INFO|ProxiFyre.ProxiFyreService|Successfully associated C:\Windows\SysWOW64\mstsc.exe to 192.168.0.5:6666 SOCKS5 proxy with protocols TCP, UDP!
2024-02-27 17:54:04.8071|INFO|ProxiFyre.ProxiFyreService|ProxiFyre Service is running...
2024-02-27 17:54:05.7607|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:04::Message::Creating SOCKS5 Local Router instance...::0
2024-02-27 17:54:05.7607|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:04::Message::SOCKS5 Local Router instance successfully created.::0
2024-02-27 17:54:05.7607|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:04::Message::Local TCP proxy for 192.168.0.5:6666 is listening port: 51304::0
2024-02-27 17:54:05.7607|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:04::Message::Local UDP proxy for 192.168.0.5:6666 is listening port: 52822::0
2024-02-27 17:54:05.7607|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:04::Message::socks5_local_router:: Detected default interface {B82AB05F-6715-4E51-BE24-3C38BB33D86C}::0
2024-02-27 17:54:05.7607|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:04::Message::SOCKS5 Local Router instance started successfully.::0
2024-02-27 17:54:18.8750|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:18::Message::Redirecting TCP: 192.168.0.10 : 51340 -> 10.9.80.181 : 3389::0
2024-02-27 17:54:18.8750|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:18::Message::NEW TCP: 192.168.0.10 : 51340 -> 10.9.80.181 : 3389::0
2024-02-27 17:54:18.8750|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:18::Message::TCP Redirect entry was found for the 10.9.80.181 : 51340 is 10.9.80.181 : 3389::0
2024-02-27 17:54:18.8750|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:18::Message::tcp_proxy_server: connect_to_remote_host:  192.168.0.5 : 6666::0
2024-02-27 17:54:20.9052|INFO|ProxiFyre.ProxiFyreService|27/02/2024 16:54:20::Message::DELETE TCP: 51340 -> 10.9.80.181 : 3389::0

Can't compile using VS 2022

Hello,

When doing build on Solution `socksify, I get 2 errors, I've looked at your documentation but don't find much info at all from the build process, I would really like to test this utility you have built but compiled myself not from binaries.

screenshot_2024-03-06_02:01:16

Have a good day

UDP relay problem

It seems ProxiFyre is not handle UDP correctly.
Here are some logs when I trying to do a UDP DNS Query to Google DNS. Hope it may help.

Application
> dnslookup www.google.com 8.8.8.8
dnslookup v1.10.0
2024/04/23 15:57:05 [fatal] Cannot make the DNS request: exchanging with 8.8.8.8:53 over udp: read udp 192.168.50.11:52582->8.8.8.8:53: i/o timeout
ProxiFyre
2024-04-23 15:56:41.9865|INFO|ProxiFyre.ProxiFyreService|Successfully associated dnslookup.exe to 127.0.0.1:1081 SOCKS5 proxy with protocols TCP, UDP!
2024-04-23 15:56:41.9865|INFO|ProxiFyre.ProxiFyreService|Successfully associated nslookup.exe to 127.0.0.1:1081 SOCKS5 proxy with protocols TCP, UDP!
2024-04-23 15:56:42.0285|INFO|ProxiFyre.ProxiFyreService|ProxiFyre Service is running...
2024-04-23 15:56:42.9659|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:41::Message::Creating SOCKS5 Local Router instance...::0
2024-04-23 15:56:42.9659|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:41::Message::SOCKS5 Local Router instance successfully created.::0
2024-04-23 15:56:42.9659|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:41::Message::Local TCP proxy for 127.0.0.1:1081 is listening port: 58763::0
2024-04-23 15:56:42.9659|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:41::Message::Local UDP proxy for 127.0.0.1:1081 is listening port: 58329::0
2024-04-23 15:56:42.9659|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:42::Message::socks5_local_router:: Detected default interface {0653D52B-CDC6-4804-BF91-0BC4741DCF5B}::0
2024-04-23 15:56:42.9659|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:42::Message::SOCKS5 Local Router instance started successfully.::0
2024-04-23 15:56:45.9975|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:45::Message::NEW client UDP endpoint:  : 58330::0
2024-04-23 15:56:45.9975|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:45::Message::Redirecting UDP 192.168.50.11 : 58330 -> 8.8.8.8 : 53::0
2024-04-23 15:56:45.9975|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:45::Message::C2S: 192.168.50.11 : 58330 -> 8.8.8.8 : 53::0
2024-04-23 15:56:45.9975|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:45::Message::C2S: 8.8.8.8 : 58330 -> 192.168.50.11 : 58329::0
2024-04-23 15:56:45.9975|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:45::Message::UDP Redirect entry was found for the 8.8.8.8 : 58330::0
2024-04-23 15:56:45.9975|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:45::Message::[SOCKS5]: associate_to_socks5_proxy: SOCKS5 ASSOCIATE SUCCESS port: 1081::0
2024-04-23 15:56:56.0569|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:55::Message::NEW client UDP endpoint:  : 52582::0
2024-04-23 15:56:56.0569|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:55::Message::Redirecting UDP 192.168.50.11 : 52582 -> 8.8.8.8 : 53::0
2024-04-23 15:56:56.0569|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:55::Message::C2S: 192.168.50.11 : 52582 -> 8.8.8.8 : 53::0
2024-04-23 15:56:56.0569|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:55::Message::C2S: 8.8.8.8 : 52582 -> 192.168.50.11 : 58329::0
2024-04-23 15:56:56.0569|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:55::Message::UDP Redirect entry was found for the 8.8.8.8 : 52582::0
2024-04-23 15:56:56.0569|INFO|ProxiFyre.ProxiFyreService|2024/4/23 15:56:55::Message::[SOCKS5]: associate_to_socks5_proxy: SOCKS5 ASSOCIATE SUCCESS port: 1081::0
Socks5 server / proxy client (shadowsocks)
2024-04-23T15:56:35.3121787+00:00  INFO tokio-runtime-worker ThreadId(15) shadowsocks_service::local::socks::server::server: crates\shadowsocks-service\src\local\socks\server\server.rs:105: shadowsocks socks TCP listening on 127.0.0.1:1081
2024-04-23T15:56:35.312255+00:00  INFO tokio-runtime-worker ThreadId(15) shadowsocks_service::local::socks::server::socks5::udprelay: crates\shadowsocks-service\src\local\socks\server\socks5\udprelay.rs:147: shadowsocks socks5 UDP listening on 127.0.0.1:1081
2024-04-23T15:56:45.4969491+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks_service::local::socks::server::socks5::tcprelay: crates\shadowsocks-service\src\local\socks\server\socks5\tcprelay.rs:196: socks5 HandshakeRequest { methods: [0, 2] }
2024-04-23T15:56:45.4972201+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks_service::local::socks::server::socks5::tcprelay: crates\shadowsocks-service\src\local\socks\server\socks5\tcprelay.rs:85: reply handshake HandshakeResponse { chosen_method: 0 }
2024-04-23T15:56:45.4974481+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks_service::local::socks::server::socks5::tcprelay: crates\shadowsocks-service\src\local\socks\server\socks5\tcprelay.rs:210: socks5 TcpRequestHeader { command: UdpAssociate, address: 0.0.0.0:0 } peer: 127.0.0.1:58764
2024-04-23T15:56:45.4976146+00:00 DEBUG tokio-runtime-worker ThreadId(02) shadowsocks_service::local::socks::server::socks5::tcprelay: crates\shadowsocks-service\src\local\socks\server\socks5\tcprelay.rs:222: UDP ASSOCIATE from 0.0.0.0:0
2024-04-23T15:56:45.4979907+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks_service::local::socks::server::socks5::udprelay: crates\shadowsocks-service\src\local\socks\server\socks5\udprelay.rs:204: UDP ASSOCIATE 127.0.0.1:58331 -> 8.8.8.8:53, 32 bytes
2024-04-23T15:56:45.4981019+00:00 DEBUG tokio-runtime-worker ThreadId(02) shadowsocks_service::local::net::udp::association: crates\shadowsocks-service\src\local\net\udp\association.rs:123: created udp association for 127.0.0.1:58331
2024-04-23T15:56:45.4982026+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks_service::local::net::udp::association: crates\shadowsocks-service\src\local\net\udp\association.rs:432: udp relay 127.0.0.1:58331 -> 8.8.8.8:53 (proxied) with 32 bytes
2024-04-23T15:56:45.4984096+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks::relay::udprelay::proxy_socket: crates\shadowsocks\src\relay\udprelay\proxy_socket.rs:103: connected udp remote <server_ip>:35889 (outbound: <server_ip>:35889) with ConnectOpts { bind_local_addr: None, bind_interface: None, tcp: TcpSocketOpts { send_buffer_size: None, recv_buffer_size: None, nodelay: false, fastopen: false, keepalive: Some(15s), mptcp: false }, udp: UdpSocketOpts { mtu: None } }
2024-04-23T15:56:45.4986075+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks::relay::udprelay::proxy_socket: crates\shadowsocks\src\relay\udprelay\proxy_socket.rs:235: UDP server client send to 8.8.8.8:53, control: UdpSocketControlData { client_session_id: 16258956041878530761, server_session_id: 0, packet_id: 1, user: None }, payload length 32 bytes, packet length 82 bytes
2024-04-23T15:56:55.5202483+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks_service::local::socks::server::socks5::tcprelay: crates\shadowsocks-service\src\local\socks\server\socks5\tcprelay.rs:196: socks5 HandshakeRequest { methods: [0, 2] }
2024-04-23T15:56:55.5204862+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks_service::local::socks::server::socks5::tcprelay: crates\shadowsocks-service\src\local\socks\server\socks5\tcprelay.rs:85: reply handshake HandshakeResponse { chosen_method: 0 }
2024-04-23T15:56:55.5209049+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks_service::local::socks::server::socks5::tcprelay: crates\shadowsocks-service\src\local\socks\server\socks5\tcprelay.rs:210: socks5 TcpRequestHeader { command: UdpAssociate, address: 0.0.0.0:0 } peer: 127.0.0.1:58771
2024-04-23T15:56:55.521021+00:00 DEBUG tokio-runtime-worker ThreadId(02) shadowsocks_service::local::socks::server::socks5::tcprelay: crates\shadowsocks-service\src\local\socks\server\socks5\tcprelay.rs:222: UDP ASSOCIATE from 0.0.0.0:0
2024-04-23T15:56:55.5216199+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks_service::local::socks::server::socks5::udprelay: crates\shadowsocks-service\src\local\socks\server\socks5\udprelay.rs:204: UDP ASSOCIATE 127.0.0.1:52583 -> 8.8.8.8:53, 32 bytes
2024-04-23T15:56:55.5217763+00:00 DEBUG tokio-runtime-worker ThreadId(02) shadowsocks_service::local::net::udp::association: crates\shadowsocks-service\src\local\net\udp\association.rs:123: created udp association for 127.0.0.1:52583
2024-04-23T15:56:55.5218668+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks_service::local::net::udp::association: crates\shadowsocks-service\src\local\net\udp\association.rs:432: udp relay 127.0.0.1:52583 -> 8.8.8.8:53 (proxied) with 32 bytes
2024-04-23T15:56:55.5221066+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks::relay::udprelay::proxy_socket: crates\shadowsocks\src\relay\udprelay\proxy_socket.rs:103: connected udp remote <server_ip>:35889 (outbound: <server_ip>:35889) with ConnectOpts { bind_local_addr: None, bind_interface: None, tcp: TcpSocketOpts { send_buffer_size: None, recv_buffer_size: None, nodelay: false, fastopen: false, keepalive: Some(15s), mptcp: false }, udp: UdpSocketOpts { mtu: None } }
2024-04-23T15:56:55.5223429+00:00 TRACE tokio-runtime-worker ThreadId(02) shadowsocks::relay::udprelay::proxy_socket: crates\shadowsocks\src\relay\udprelay\proxy_socket.rs:235: UDP server client send to 8.8.8.8:53, control: UdpSocketControlData { client_session_id: 6241320567857523883, server_session_id: 0, packet_id: 1, user: None }, payload length 32 bytes, packet length 82 bytes
2024-04-23T15:57:58.1983479+00:00  INFO                 main ThreadId(01) shadowsocks_rust::monitor::imp: src\monitor\windows.rs:10: received CTRL-C, exiting

Option to disable protocol (tcp)

I do not need to proxy tcp connections, and am trying to reduce bandwidth usage on my proxy, I recently fell in love with this but there is one thing that I really want and that is not tcp
This would be the cherry on the cake for me, thank you so much for conceiving such beautiful offspring.

Error at startup with Server 2003 SP2

Hello.
I tried running ProxiFyre on 2003 SP2 32-bit with One Core API. Is it possible to fix this error?

Configuration Result:
[Success] Name ProxiFyreService
[Success] DisplayName ProxiFyre Service
[Success] Description ProxiFyre - SOCKS5 Proxifier Service
[Success] ServiceName ProxiFyreService
Topshelf v4.3.0.0, .NET Framework 4.8.4526.0 (4.0.30319.42000)
Topshelf.Hosts.ConsoleRunHost Error: 0 : An exception occurred, System.Runtime.InteropServices.SEHException (0x80004005):
...

start error.txt

Adding appNames

Hi, please hrelp me to add appNames for apps like LDPlayer (android emulator). I used the following appNames, but it didn't work.

"appNames": ["LDPlayer9", "D:\\LDPlayer\\LDPlayer9\\LDPlayer.exe", "LDPlayer9.exe", "LDPlayer.exe"],

A few configuration questions.

  1. What values can the "logLevel" parameter take in the app-config.json file?

  2. How to write applications to the "appNames" parameter, by the name of the window, by the name of the process, and if by the name of the process, do I need to add the .exe extension?

  3. If there is no authorization on the proxy server, what should I do with the parameters "username" and "password", delete or can I leave it, since there is no authorization?

  4. Does the developer plan to add the ability to run ProxiFyre from a BAT script with parameters, ignoring the app-config.json file?

Thanks.

Behavior of the config file

{
 "logLevel": "None",
 "proxies": [
         {
         "appNames": ["program.exe"],
         "socks5ProxyEndpoint": "proxy.test.com:5256",
         "supportedProtocols": ["TCP", "UDP"]
         },
         {
         "appNames": ["program.exe"],
         "socks5ProxyEndpoint": "proxy.test.com:5257",
         "supportedProtocols": ["TCP", "UDP"]
         },
     ]
}
  1. I would like to know what is the behavior when adding twice the same program, does it override the previous one?
  2. If I add another program with supportedProtocols: [] // Empty, does it override the previous one and remove the proxification?

socksify ip address

please consider to support also destinations ip address directly
so we can socksify the entire system and not just "appNames"

AllowIP: 0.0.0.0/0
DisallowIP: 192.168.10.0/20, 10.100.50.64/32

Accidental shutdowns

Hello there, sir.
Thanks for a great tool!
I have a question - is there any way for you to change app close logic? The app closes after pressing any key, even ALT+TAB closes proxifyre.
Could you please make it close by pressing CTRL+C for example?

binaries

please consider to release windows binaries

Could not load file or assembly 'socksify.dll' or one of its dependencies

Hi, after running it reports:

An exception occurred, System.IO.FileNotFoundException: Could not load file or assembly 'socksify.dll' or one of its dependencies. The specified module could not be found.
File name: 'socksify.dll'
at ProxiFyre.ProxiFyreService.Start()
at Topshelf.ServiceConfiguratorExtensions.<>c__DisplayClass2_01.<WhenStarted>b__0(T service, HostControl control) at Topshelf.Builders.DelegateServiceBuilder1.DelegateServiceHandle.Start(HostControl hostControl)
at Topshelf.Hosts.ConsoleRunHost.Run()

image

System is Windows 11 22H2, I tried to install Microsoft VC_redist.x64 (1) (2015-2022). It did not help.

Problem with logging using proxifyre.exe

Dear Sir

I am writing to report a problem with logging using the proxifyre.exe command line tool. I have followed the instructions on the documentation, but I cannot see any results or logs.

The command I used was: proxifyre.exe -log-level all

The expected output was: A log file containing detailed information about the proxy settings and connections.

The actual output was: Nothing. No log file was created or displayed.

I have tried to troubleshoot the problem by checking the permissions, firewall settings, and proxy configuration, but nothing worked. I am using Windows 10 64-bit and the latest version of proxifyre.exe.

I would appreciate it if you could look into this issue and provide a solution or a workaround. Thank you for your time and attention.

Topshelf.Hosts.StartHost Error: 0 : The service failed to start., System.ServiceProcess.TimeoutException:

Dear Sir,
Thank you very much for your contribution to the tool. I try to launch it by ".\ProxiFyre.exe start" in admin powerShell, but I got the following error,

"Configuration Result:
[Success] Name ProxiFyreService
[Success] DisplayName ProxiFyre Service
[Success] Description ProxiFyre - SOCKS5 Proxifier Service
[Success] ServiceName ProxiFyreService
Topshelf v4.3.0.0, .NET Framework 4.8.9181.0 (4.0.30319.42000)
Topshelf.Hosts.StartHost Error: 0 : The service failed to start., System.ServiceProcess.TimeoutException:
System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
Topshelf.Runtime.Windows.WindowsHostEnvironment.StartService(String serviceName, TimeSpan startTimeOut)
Topshelf.Hosts.StartHost.Run()"

My system is windows 10 and I wonder could you give any opinion about what is happening? Thank you very much for your help.

Can't make ProxiFyre work with proxy

Hi, I have installed Windows Packet Filter 3.4.8 driver and downloaded ProxiFyre-v1.0.18-x64-signed.zip, after that I created app-config.json file (with rule for the 'iexplore.exe') and started ProxiFyre.exe. After that I run my proxy server and expect traffic translation for IE Browser but I get nothing at all, after I run the ProxiFyre browser can't get access to any of the pages no matter HTTP or HTTPS.

Also tried to run tools_bin_x64/socksify.exe it doesn't work either.

I tried different proxy servers: CCProxy\3proxy\some random github: C++ Socks5 servers and also C# socks5 servers, same story - nothing works at all.

All tested socks5 servers work fine in browsers when I use them without ProxiFyre

What I do wrong?

config file

{
 "logLevel": "Info",
 "proxies": [
         {
         "appNames": ["iexplore.exe"],
         "socks5ProxyEndpoint": "127.0.0.1:3333",
         "supportedProtocols": ["TCP", "UDP"]
         },
         {
         "appNames": ["firefox.exe"],
         "socks5ProxyEndpoint": "127.0.0.1:3333",
         "supportedProtocols": ["TCP", "UDP"]
         }
     ]
}

Incompatiblity with mitmproxy

there is this application called 'proxifier' which worked for my goal, but i wanted it runnable with .bat (and no subscription)

ive been trying to find a proxy app where i can force traffic from an application to a proxy server
this project seemed perfect to the fact it can support my target application called 'roblox' and filter excusively to that

i have started up a proxy server, specifically mitmproxy, that listens on localhost:8080
and started proxifyre that redirects traffic to said destination

as a test, i configured the proxifyre to redirect chrome traffic

immediately, there was a problem: the results did not follow my expectations
the following is the console of mitmproxy
reality
(by the way i should be able to see 'client disconnect' without closing proxifyre)

and this was what i was expecting
expectation

for this second image, i set my system proxy to localhost:8080

but some applications like roblox seem to ignore the system proxy
which is why i need something like this project to force the traffic

if you could either tell me how to fix this, fix this problem, or recommend me another open source that will work for my goal, please do
thanks in advance

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.