Socksify or Proxifyre not tunneling without error

[devman]

I’ve tried both Proxifyre and Socksify and I could not make it work, but Wiresock is working perfectly.

Here’s the what I did on Proxifyre:

1. I opened a socks proxy
   • First I tried with SSH command ssh root@SERVER_IP -D 8080
   • Second I tried with Socks inbound of v2rayN
2. I’ve run .\ProxiFyre.exe run (You can see below the app-config.json file)

app-config.json:

json
{
"logLevel": "Deb",
"proxies": [
{
"appNames": [
"firefox",
"Telegram.exe"
],
"socks5ProxyEndpoint": "127.0.0.1:8080",
"supportedProtocols": [
"TCP"
]
}
]
}

Logs of Proxfyre:

2024-05-29 14:25:33.1523|INFO|ProxiFyre.ProxiFyreService|ProxiFyre Service has stopped.
2024-05-29 14:25:34.8452|INFO|ProxiFyre.ProxiFyreService|Successfully associated firefox to 127.0.0.1:8080 SOCKS5 proxy with protocols TCP!
2024-05-29 14:25:34.8852|INFO|ProxiFyre.ProxiFyreService|Successfully associated Telegram.exe to 127.0.0.1:8080 SOCKS5 proxy with protocols TCP!
2024-05-29 14:25:34.9637|INFO|ProxiFyre.ProxiFyreService|ProxiFyre Service is running...
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:34 AM::Message::Creating SOCKS5 Local Router instance...::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:34 AM::Message::SOCKS5 Local Router instance successfully created.::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:34 AM::Message::Local TCP proxy for 127.0.0.1:8080 is listening port: 2142::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:34 AM::Message::socks5_local_router:: Detected default interface {B404DFD0-745B-4C91-B5C7-BA78647826B8}::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:34 AM::Message::SOCKS5 Local Router instance started successfully.::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:35 AM::Message::Redirecting TCP: 192.168.1.100 : 2143 -> 5.9.210.65 : 443::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:35 AM::Message::NEW TCP: 192.168.1.100 : 2143 -> 5.9.210.65 : 443::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:35 AM::Message::Redirecting TCP: 192.168.1.100 : 2144 -> 216.239.38.120 : 443::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:35 AM::Message::NEW TCP: 192.168.1.100 : 2144 -> 216.239.38.120 : 443::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:35 AM::Message::Redirecting TCP: 192.168.1.100 : 2089 -> 5.9.210.65 : 443::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:35 AM::Message::NEW TCP: 192.168.1.100 : 2089 -> 5.9.210.65 : 443::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:35 AM::Message::Redirecting TCP: 192.168.1.100 : 2132 -> 91.108.56.141 : 443::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:35 AM::Message::NEW TCP: 192.168.1.100 : 2132 -> 91.108.56.141 : 443::0
2024-05-29 14:25:35.8602|INFO|ProxiFyre.ProxiFyreService|5/29/2024 10:55:35 AM::Message::Redirecting TCP: 192.168.1.100 : 2133 -> 91.108.56.141 : 80::0
#... and many other similar logs...

And here’s the socksify log:

PS C:\Users\dev\Desktop\tools> .\socksify
WinpkFilter is loaded

Available network interfaces:

1) WAN Network Interface (BH)
2) WAN Network Interface (IPv6)
3) WAN Network Interface (IP)
4) Local Area Connection* 2
5) Ethernet
6) Local Area Connection* 1
7) vEthernet (WSL (Hyper-V firewall))
8) vEthernet (Default Switch)
9) Wi-Fi

Select interface to filter:5

Application name to socksify: firefox

SOCKS5 proxy IP address: 127.0.0.1

SOCKS5 proxy port: 8080

Local port for the transparent TCP proxy server: 9000

SOCKS5 USERNAME[optional]:

SOCKS5 PASSWORD[optional]:
No suitable username or password specified, using anonymous authentication with SOCKS5 proxy
Press any key to stop filtering

I even tried to restart Firefox but still no logs for redirecting on socksify

(I’m using Windows 11)

• This topic was modified 6 months, 3 weeks ago by devman.
• This topic was modified 6 months, 3 weeks ago by devman.

[Vadim Smirnov]

Could you please disable Windows Firewall (or any other firewall you might have) and check if the issue persists?

[devman]

Looks like the problem was on my end and I should’ve added the Proxyre to the firewall allowed apps.

[Author]

Posts