Proxifier is a network gateway that allows applications that do not support working through proxy servers to operate through a SOCKS or HTTPS proxy, without having to re-route all traffic through the proxy network. Using Proxifier, it’s possible to route applications through a single entry point on Nimble IP and direct each one to the relevant IP pipeline.
To begin working with Proxifier, download and install the application from the Proxifier website.
In this guide, we will be using Windows as an example, although setting up on macOS is very similar and follows the same configuration steps.
To connect Proxifier with Nimble IP, you will need to create a profile - click on the ‘Profile’ tab at the top left, and from the drop-down menu select ‘Proxy Servers’.
2. Click “Add” to set Nimble IP as a proxy server.
3. Enter the following server information:
Address ⇒ ip.nimbleway.com
Port ⇒ 7000
Protocol ⇒ HTTPS
4. Authentication This is when you need to decide which Nimble pipeline you would like to use, determined by the pipeline name in the username connection string. Your Nimble account comes pre-configured with one pipeline for a quick start, and your account manager will provide you with its username and password. We will discuss the option for adding additional pipelines in the “Setting proxy rules” section below.
Check the box to enable username and password authentication
Username ⇒ Nimble’s username string: account-[accountName]-pipeline-[pipelineName]
Password ⇒ Nimble’s pipeline password
5. To verify the setup was successful, click on ‘Check’ and Proxifier will test the connection and report back its status.
6. Once you receive confirmation that the connection is set up correctly, go back to the main Proxifier window and click “OK” to save your profile.
Note: We recommend you do not set Nimble IP as your default proxy server as this may result in an unwanted amount of traffic going through Nimble.
So far, we have covered how to connect a single pipeline from Nimble to Proxifier. Now it’s time to decide in which scenarios this connection should be used, and whether you need to connect multiple Nimble pipelines.
In case the requests you send through Nimble should all have the same session behavior and targeting (location, IP rotation, session control, etc.), the profile previously created is all you need. We suggest you configure your session preferences in the Nimble pipeline, as it will help our optimization engines select more relevant IPs for your use case. Check out our Admin API documentation for more details on how to configure your pipelines.
If you have multiple use cases, each with its own proxy connection requirements, there are two ways to control the session behavior for each case:
Create multiple pipelines in Nimble IP, one for each profile in Proxifier. As previously mentioned, this helps our optimization engines tune in to your needs faster. Read more on the use of pipelines and their available configurations.
Use the username string set in each Proxifier profile to configure the proxy connection and session behavior. Read more about Nimble Backconnect Gateway API and possible configurations.
We’ll now connect various applications and scenarios to the Proxifier profiles that channel each one through Nimble IP.
Click on the ‘Profile’ tab again, but this time choose ‘Proxification rules’.
In the rules window, select the profiles created for use with Nimble:
Set the applications that are allowed to access each Nimble pipeline.
In case your proxy use cases are split by domain or port, you have the option to set those as part of your rules as well.
In order to improve your data-gathering success, DNS resolution should be done by Nimble IP.
Under the Profiles menu, select ‘Name Resolution’.
2. Under ‘Proxifier DNS settings’ select ‘Resolve hostnames through proxy’.
Click ‘OK’ at the bottom and you are ready to go!
