How to connect Bitvise programs with Proxifier on the PC
The use of the Bitvise program with Proxifier is common among many Indonesians. For some people, using Bitvise means opening a connection from the server and accessing it, be it remote desktop, terminal and others. However, for some people, using Bitvise is only used as an intermediary that can be determined by yourself Header which is sent to the server.
Sometimes nice Header sent in the form of host or replace host Main server and sometimes you have to use help to do this Squid proxy. While the use of Proxifier serves to channel connections received from Bitvise to all existing programs. So Bitvise is only used here as an intermediary to connect SSH and assign to localhost which it is picked up by Proxifier.
This may be difficult to understand, but using Bitvise with Proxifier is very easy because Users just have to set something in the program and you don’t have to redirect any confusing code. In this article, I’ll explain how to do it, and I guarantee users will be able to understand it even if they have to try multiple times. But if the user can do it once, the next one will certainly not even be able to find that path. Here is the tutorial, see below.
Please open Bitvise first and make sure you have an SSH account. First, enter the SSH account in the login field.
When you have it filled out, just go to the tab Options and look at that When logging in, please deactivate all.
Go to tab Services, in section SOCKS / HTTP proxy forwarding fill it in like this. Here the example uses “1082” as the list port.
Then please log in to SSH from Bitvise, and when it is connected, enter the proxifier.
In the proxifier program, click the option profile => Proxy server => Add to.
There is a dialog for loading the server. Enter in the Server Address field 127.0.0.1 and enter in the port section 1082. And for the protocol please choose one, but I suggest choosing SOCKS5 as the connection is more stable.
The last step just hit the button OK and try opening a browser and checking the IP address, it should be properly connected to SSH.
Above I have not provided a method of populating the SSH server as I think users can already do it. The point is, the listen port was what was really needed to connect over the link localhost. And I prefer SOCKS5 because I think HTTP isn’t very fast when used rummage. Above I said to disable the sections like Remote Desktop, Terminal and SFTP as they are not useful and users only need one connection. If you have anything to ask, please comment.
Hopefully useful and good luck
