wiresock / proxifyre Goto Github PK
View Code? Open in Web Editor NEWProxiFyre: SOCKS5 Proxifier for Windows
Home Page: https://www.ntkernel.com
License: GNU Affero General Public License v3.0
ProxiFyre: SOCKS5 Proxifier for Windows
Home Page: https://www.ntkernel.com
License: GNU Affero General Public License v3.0
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):
...
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```
{
"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"]
},
]
}
It sounds crazy, but the idea is that all applications and programs that work with the network send traffic to a proxy server, I need it. I think we need to add the '*' parameter to the appNames to enable this idea.
Cool tool! Thank you
is there a way of editing the config file without having to restart the program?
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()
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"]
}
]
}
Hello!
I installed ProxiFyre as Windows 11 service. My config:
{
"logLevel": "None",
"proxies": [
{
"appNames": ["browser.exe"],
"socks5ProxyEndpoint": "IP_ADDR:PORT",
"username": "LOGIN",
"password": "PASSWORD",
"supportedProtocols": ["TCP", "UDP"]
}
]
}
(I proxy Yandex.Browser)
Proxying works fine. Then I restart Windows. After logon I see that ProxiFyre service is running. Then I launch Yandex.Browser. But there is no proxying. I restart ProxiFyre service (sometimes several times) and it helps - proxying starts to work. Sometimes restarting ProxiFyre service doesn't help, but restarting Yandex.Browser helps.
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?
is it possible to use a wildcard to catch everything?
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!
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.
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.
> 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
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
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
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.
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"],
[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.9241.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()```
Hi,
Love to see a free open-sourced alternative to proxifier, but could you please add support for http(s) proxy and additional support command line for function like add/remove app profile?
Thank you
Fyi, after few minutes, using proxifyre on win8.1, the nic connectivity loose ip address and network totally crash.
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
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?
Thanks for the binaries
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
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.
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
What values can the "logLevel" parameter take in the app-config.json file?
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?
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?
Does the developer plan to add the ability to run ProxiFyre from a BAT script with parameters, ignoring the app-config.json file?
Thanks.
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
(by the way i should be able to see 'client disconnect' without closing proxifyre)
and this was what i was expecting
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
please consider to release windows binaries
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.DelegateServiceBuilder
1.DelegateServiceHandle.Start(HostControl hostControl)
at Topshelf.Hosts.ConsoleRunHost.Run()
System is Windows 11 22H2, I tried to install Microsoft VC_redist.x64 (1) (2015-2022). It did not help.
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:
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
The overall network of the host is heavily congested,
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.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.