Backconnect in a browser
Residential proxy backconnect in a browser
Browser extensions
We recommend setting up a backconnect proxy in the SwitchyOmega browser extension. It's supported on Firefox as well as Chrome and other browsers derived from it.
SwitchyOmega supports proxy profile creation, which means that the username and password can be entered and saved before the connection attempt.
Please refer to our SwitchyOmega setup guide to install the extension.
The FoxyProxy extension supports this functionality as well. Find the setup guide.
Backconnect
Firstly, check out our backconnect documentation to understand how it works:
Backconnect overview and examples
Setting up
We are skipping to the Step 3 of the SwitchyOmega setup guide.
In this example, we are going to create a profile for a 30 minute sticky proxy that is going to return IPs from Nashville, TN, United States.
Creating a new profile:
Server and Port
Set the Protocol to HTTP. When using backconnect, the server will always be gate.smartproxy.com
, and the port will always be 7000
. The location and the session type of the proxy are going to be specified in the username.
Backconnect authentication
Click on the lock icon to the right of the Port input field to access the authentication window:
This is where the magic happens. A username like this is going to be used as an example:
user-SPuser-country-US-city-Nashville-session-nashville30-sessionduration-30
Refer to the backconnect overview and the guide to learn how to make a username for the location you need.
Make sure to save and apply the changes to the profile.
Sessions
Use a different session variable for each profile you create to make sure that two profiles do not receive the same IP address.
Usage
Clicking on the SwitchyOmega icon will list all of the created profiles.
We are going to click on the US Nashville Sticky 30 profile we have created to turn it on.
Finally, we check the IP address on https://smartproxy.com/what-is-my-ip to make sure that the proxy works.
Note: Whitelisted IP
Make sure that your IP address is not whitelisted on our dashboard. A browser will ignore your backconnect username and will authenticate using the whitelisted IP instead.
Updated 4 months ago