Open Ahmad-2213 opened 6 months ago
Could you please try the WireSock VPN Client build 1.2.39 linked to this forum topic?
Could you please try the WireSock VPN Client build 1.2.39 linked to this forum topic?
Can't Open the wiresock-client.exe on Windows 10 . Should I Try to uninstall the previous versions and then try again?
I don't think I understand what is happening. Have you installed the this build? If anything goes wrong try uninstalling the software, reboot and install it again.
I don't think I understand what is happening. Have you installed the this build? If anything goes wrong try uninstalling the software, reboot and install it again.
I tried all of it , But still Can't run the program...
The application in the screenshot is the command line WireSock VPN Client, which lacks a graphical user interface. For more information, visit this link. If you prefer a graphical interface, please also download and install WireSockUI which will run as an UI front end.
The application in the screenshot is the command line WireSock VPN Client, which lacks a graphical user interface. For more information, visit this link. If you prefer a graphical interface, please also download and install WireSockUI which will run as an UI front end.
There's no actual UI for this version. Do you have any suggestions? If you're going to fix this for the next version , So I'll be waiting for that surely!
- Download and install WireSock VPN Client v1.2.39 using the link above.
- Download and run the latest available WireSockUI.
Still doesn't work , I guess I'm doing something wrong. Don't mean to bother you anymore...
Try removing all components, restarting your system, and starting the installation process from scratch. The only difference now is that you are using a more recent build of the WireSock VPN CLI, which was not an issue when you initially got it running successfully.
- Download and install WireSock VPN Client v1.2.39 using the link above.
- Download and run the latest available WireSockUI.
So I removed All of the components and did the same as you said, however, It's still not working...
and this is captured with CLI version:
Please note that uou should not use square brackets in the command line. If path does not contain spaces you can also omit the quotes.
Please note that uou should not use square brackets in the command line. If path does not contain spaces you can also omit the quotes.
I fixed that. Still encountering troubles with connecting to the config. I'll also put my config down here to see if everything's right!
Ah, I see the issue now. You are attempting to use a SOCKS5 proxy at the address 127.0.0.1:2080. Please note that the localhost address is not supported for this purpose. If this is a standard SOCKS5 proxy, using it in this manner is generally ineffective as it will simply relay the original handshake. However, if the SOCKS5 proxy is configured with Shadowsocks, this setup might be useful. I will consider adding support for such configurations in the future.
Ah, I see the issue now. You are attempting to use a SOCKS5 proxy at the address 127.0.0.1:2080. Please note that the localhost address is not supported for this purpose. If this is a standard SOCKS5 proxy, using it in this manner is generally ineffective as it will simply relay the original handshake. However, if the SOCKS5 proxy is configured with Shadowsocks, this setup might be useful. I will consider adding support for such configurations in the future.
I really appreciate that. my last question is : is this going to tunnel the handshake or it'll detour all of the data through the proxy? similarly in OpenVPN , the proxy is used to work as a chain meaning that the traffic is passed into the proxy and then going to the server. my point is that I want to bypass the censorship of TLS Handshake by tunneling via proxy , not to route all of my data through it.
Only the Wireguard handshake is routed through the SOCKS5 proxy because it is the most easily detected part of the protocol. All other Wireguard data packets are transmitted directly. You can refer my post for the details.
Ah, I see the issue now. You are attempting to use a SOCKS5 proxy at the address 127.0.0.1:2080. Please note that the localhost address is not supported for this purpose. If this is a standard SOCKS5 proxy, using it in this manner is generally ineffective as it will simply relay the original handshake. However, if the SOCKS5 proxy is configured with Shadowsocks, this setup might be useful. I will consider adding support for such configurations in the future.
yes I'm using Shadowsocks on Nekoray Client.
Hello There! are there any scheduals for new update?
I don't have an estimate for local SOCKS5 proxy support yet, but it is on my to-do list.
Hello There! are there any scheduals for new update?
I am also looking forward to the addition of local SOCKS5 proxy support feature, but until then, there is a workaround that somewhat addresses this issue. In the WireSock settings, add the Nekoray app and its used cores in the Disallowed apps section so that Nekoray does not use this WireSock connection. Then, set Nekoray to Tun mode and activate the desired proxy. Now you can activate WireSock.
DisallowedApps = nekobox_core,nekoray,xray,sing-box
Hello There! are there any scheduals for new update?
I am also looking forward to the addition of local SOCKS5 proxy support feature, but until then, there is a workaround that somewhat addresses this issue. In the WireSock settings, add the Nekoray app and its used cores in the Disallowed apps section so that Nekoray does not use this WireSock connection. Then, set Nekoray to Tun mode and activate the desired proxy. Now you can activate WireSock.
DisallowedApps = nekobox_core,nekoray,xray,sing-box
Well , the benefits of using SOCKS5 proxy is that We don't need to Tunnel the traffic through Nekoray's Core. Instead , we just tunnel the handshake to go through proxy to keep the connection alive. The case you're mentioning just slows down the Connection. better way is to just pass the handshake through Nekoray , Not all of the Data.
Hello There! are there any scheduals for new update?
I am also looking forward to the addition of local SOCKS5 proxy support feature, but until then, there is a workaround that somewhat addresses this issue. In the WireSock settings, add the Nekoray app and its used cores in the Disallowed apps section so that Nekoray does not use this WireSock connection. Then, set Nekoray to Tun mode and activate the desired proxy. Now you can activate WireSock. DisallowedApps = nekobox_core,nekoray,xray,sing-box
Well , the benefits of using SOCKS5 proxy is that We don't need to Tunnel the traffic through Nekoray's Core. Instead , we just tunnel the handshake to go through proxy to keep the connection alive. The case you're mentioning just slows down the Connection. better way is to just pass the handshake through Nekoray , Not all of the Data.
Yes, that's correct. The method I mentioned is only temporary until the local SOCKS5 proxy support feature is added to the application. Additionally, you can use a proxy that another device on your local network has shared.
The Connection can not be stablished via Socks5 proxy.