Skype supports both the UDP and TCP protocols. By default it uses UDP, but it switches to TCP if UDP is
blocked. If you have a SOCKS5 or a Shadowsocks proxy, create a redirect rule for Skype.exe, specify both the UDP and TCP
transports. If you have a TCP-only proxy such as HTTPS, SOCKS4, or SSH,
1. Create a block rule for Skype.exe, specify the UDP transport.
2. Create a redirect rule for Skype.exe, specify the TCP transport.
Examine the error log (right click on the ProxyCap taskbar icon, choose “Status and Logs”, select the
Error Log tab). If it's empty, check the proxy using the integrated proxy checker (right-click on the ProxyCap
taskbar icon, choose “Configuration”, open the Proxies category, select the proxy from the list, press
the Check Proxy Server button on the toolbar).
Usually, this problem is caused by incorrect or incomplete information specified in the redirect rule. To troubleshoot this
problem, try the following:
1. Create a “catch all” (for all programs) redirect rule.
2. Open the Connections status screen (right click on the ProxyCap taskbar icon, choose “Status and Logs”, select
the Connections tab). Tick “Always on top” on the right bottom of the dialog box.
3. Run the program that needs to be tunneled, and watch the status.
With SSH, ProxyCap uses state of the art encryption techniques for all data transmitted between your computer and
the SSH server. The program supports SSH public key authentication, the most secure method, and allows you to verify
the identity of the SSH server (to use this, you must enable host key verification and import the server's public key).
ProxyCap can redirect UDP through a SOCKS5 or a Shadowsocks proxy or a chain of UDP capable proxies. The required condition is
that UDP relay must be enabled on the proxy server. Also, if you want to run streaming software or online games from behind
a proxy you need to ensure that the connection to the proxy is fast enough.
ProxyCap doesn't work. I have other proxifier installed.
Other proxifiers can prevent ProxyCap from functioning properly if installed on the same PC. In order to make ProxyCap
function properly, you need to uninstall other proxifier and then to re-install ProxyCap.
To solve the issue, please do the following:
1. Determine the location of wsl.exe on your computer. If you installed the MS Store version of WSL, it would be something like:
“C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.3.0_x64__8wekyb3d8bbwe\wsl.exe”.
2. Download https://www.proxycap.com/download/nolsp.zip, unpack the archive.
3. Run Administrator command prompt and enter: nolsp.exe <full_path_to_wsl.exe>
VirtualBox stops working after installing ProxyCap.
To solve the issue, please do the following:
1. Determine the location of the file VirtualBoxVM.exe on your computer. It should be like:
“C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe”.
2. Download https://www.proxycap.com/download/nolsp.zip, unpack the archive.
3. Run Administrator command prompt and enter: nolsp.exe <full_path_to_VirtualBoxVM.exe>
I get “Your system configuration is no longer compatible with ProxyCap”.
This error message means that there is a conflict between ProxyCap and some other program installed on your PC.
Please note that other proxifiers/socksifiers can prevent ProxyCap from functioning properly if installed on the same
PC.
ProxyCap stopped working when I upgraded to a new version of Windows.
Most likely the latest version of ProxyCap supports your new Windows version (an up-to-date list of officially supported versions of
Windows can be found here). Upgrade ProxyCap to the latest version. If you already have the latest version
of ProxyCap installed then reinstall the program.
We offer a library which you can integrate into your application. The library offers an easy to use API, which allows you to e.g.
set proxies, routing rules and DNS settings and retrieve error log entries. Further details are available on request.
