Wiss Proxy

Proxies

Configure proxies in the username

Geo, OS, and IP rotation right in the rotating proxy line

For Residential and Mobile, all settings live in the login. The bot builds it for you, but you can edit it by hand: the next connection uses the new settings.

  • No need to get data in the bot again.
  • The password stays the same.
  • Old lines keep their own settings, all of them share the traffic.

ISP and Datacenter have a fixed IP and no login parameters.

The line

pool.wissproxy.com:10000:LOGIN_c_US_s_a1b2_ttl_10m:PASSWORD
  • Host – pool.wissproxy.com, the same for everyone.
  • Port – any from 10000 to 10999. HTTP and SOCKS5 work on the same port.
  • Login – your login plus the parameters after it. The login without parameters is everything before the first _.
  • Password – the same with any parameters.

In the examples below, replace LOGIN and PASSWORD with your own.

Parameters

Each parameter is written as _key_value at the end of the login.

ParameterExampleWhat it sets
_c__c_UScountry, a two-letter code
_sd__sd_2928region or state, numeric code only
_city__city_New-Yorkcity in Latin letters, spaces become -
_asn__asn_7922provider or carrier by AS number
_zip__zip_10001postal code, only together with _c_
_os__os_windowsdevice OS: windows, macos, linux, android
_s__s_a1b2session, pins the IP
_ttl__ttl_10mhow long the session keeps the IP, only together with _s_

Skip the parameters you do not need and keep the rest in the bot's order:

LOGIN_c_COUNTRY_sd_REGION_city_CITY_asn_PROVIDER_zip_ZIP_os_OS_s_SESSION_ttl_TIME

Values may contain only Latin letters and digits, plus - in a city or ZIP. The whole login must stay within 128 characters. Old lines with _isp_ and a number keep working: that is a provider by an internal code.

How the IP changes

LoginWhat happens
LOGIN_c_USa new IP for every connection
LOGIN_c_US_s_a1b2_ttl_10mthe IP is kept for 10 minutes, then changes
LOGIN_c_US_s_a1b2Sticky: the IP is kept while the device is online
  • _s_ – any name of Latin letters and digits, for example _s_job1. The same name gives the same IP, a new name gives a new IP.
  • _ttl_ – a number and a unit: s seconds, m minutes, h hours. For example _ttl_30s, _ttl_10m, _ttl_1h. The bot offers _ttl_1m to _ttl_24h.
  • Idle – a session with no traffic closes after 60 minutes. The next request with the same _s_ gets a new IP.
  • Sticky – a home or mobile device stands behind the IP. If it goes offline, the IP changes or the request returns an error.
  • Without _s_ – a connection that a program keeps open uses one IP until it closes.

Changing the geo – change _s_ too. With the old session the gateway returns the old IP and ignores the new geo.

LoginResult
LOGIN_c_US_sd_2928_s_job1_ttl_30man IP from Texas
LOGIN_c_DE_s_job1_ttl_30mthe same IP from Texas
LOGIN_c_DE_s_job2_ttl_30man IP from Germany

Geo

  • Country – _c_ and a two-letter code: _c_US, _c_DE, _c_FR. The United Kingdom is GB, not UK. Without _c_ the IP comes from any country.
  • Region – _sd_ and a numeric code: _sd_2928 is Texas. A name like _sd_Texas or an abbreviation like _sd_TX returns 407. US state codes are below. For other countries, pick the region in the bot, tap Get data, and take the number after _sd_.
  • City – _city_ and the English name joined with -: _city_Dallas, _city_New-York. Add the country too: the same city names exist in different countries.
  • Provider – _asn_ and the autonomous system number, digits only. With letters, _asn_AS7922 returns 407. Available providers are in the bot: Location → Provider, for Mobile Operator.
  • ZIP – _zip_ and a postal code, only with a country: _c_US_zip_10001. Capital letters, spaces become -: _c_CA_zip_M5V. The gateway picks the nearest IP, so the exit postal code may differ.
CountryProviderParameter
USAComcast_asn_7922
USAVerizon_asn_701
GermanyVodafone_asn_3209
US state codes
StateCodeStateCode
Alabama79Montana1783
Alaska82Nebraska1888
Arizona155Nevada1895
Arkansas156New Hampshire1898
California443New Jersey1900
Colorado596New Mexico1901
Connecticut603New York1906
Delaware667North Carolina1949
District of Columbia759North Dakota1952
Florida898Ohio2111
Georgia941Oklahoma2117
Hawaii1072Oregon2142
Idaho1130Pennsylvania2218
Illinois1154Rhode Island2459
Indiana1168South Carolina2745
Iowa1175South Dakota2746
Kansas1285Tennessee2923
Kentucky1330Texas2928
Louisiana1561Utah3101
Maine1616Vermont3147
Maryland1675Virginia3173
Massachusetts1684Washington3211
Michigan1728West Virginia3234
Minnesota1742Wisconsin3250
Mississippi1752Wyoming3255
Missouri1753

The codes are the same for Residential and Mobile, but Mobile covers fewer states. If a state is not listed in the bot, a string with its code returns 503.

Every filter narrows the IP choice. Country, region, and city together usually work. A city together with a ZIP or provider often returns 503. Got 503 – remove filters one by one, starting with the narrowest.

Threads

  • Ports – each port from 10000 to 10999 is a separate channel, up to 1000 IPs at once.
  • Sessions – with _s_, the session sets the IP, not the port. One session on different ports gives one IP. Give each thread its own session: _s_job1, _s_job2.
  • Bot export – every line already has its own port and its own session.
  • Traffic – shared by all lines of the package. Changing parameters costs nothing.

Examples

What you needLogin
USA, a new IP for every connectionLOGIN_c_US
Texas, the IP is kept for 30 minutesLOGIN_c_US_sd_2928_s_tx1_ttl_30m
Dallas, the IP is kept while the device is onlineLOGIN_c_US_sd_2928_city_Dallas_s_dal1
Dallas by ZIP, a new IP every 10 minutesLOGIN_c_US_zip_75201_s_dal2_ttl_10m
Germany, Vodafone networkLOGIN_c_DE_asn_3209
USA, Windows devicesLOGIN_c_US_os_windows
United Kingdom, a new IP every hourLOGIN_c_GB_s_uk1_ttl_1h

The same line in different formats:

socks5://LOGIN_c_US_sd_2928_s_tx1_ttl_30m:PASSWORD@pool.wissproxy.com:10000
http://LOGIN_c_US_sd_2928_s_tx1_ttl_30m:PASSWORD@pool.wissproxy.com:10000

Check

bash
curl -x 'http://LOGIN_c_US_sd_2928:PASSWORD@pool.wissproxy.com:10000' https://ipinfo.io/json

The response shows the exit IP, country, region, and city. Run it twice: without _s_ the IP changes, with _s_ it stays the same. Different IP lookup services may place the same address in neighbouring cities.

Errors

ResponseCauseWhat to do
407a typo in a parameter, a region as a word, AS in the provider number, ZIP without a country, wrong password, package term endedcompare the login with the parameter table, check the package in the bot
503 No exit nodeno IPs for these filters right nowremove the narrowest filter, change _s_, retry
IP does not change_s_ without _ttl_, or the connection stays openremove _s_, add _ttl_, or change the session
Geo did not changethe old session is still in the loginset a new _s_ value

In the first 10 minutes after purchase, lines may return 503: the package is being connected. With _s_, the first request occasionally gets 503 if the device has just gone offline. Enable retries on error in your program.

The _rotm_ parameter

The bot does not set it. It defines what happens when the session device goes offline. It goes at the very end of the login, only together with _s_.

  • _rotm_0 – switch to another device right away. This is the gateway default.
  • _rotm_1 – wait about 5 seconds. Requests may get errors meanwhile.
  • _rotm_2 – never switch the device. The line stops working until you change _s_. For accounts where an IP change is worse than an error.

How this maps to the bot

In the botIn the login
Country_c_
Region_sd_
City_city_
Provider or Operator_asn_
ZIP_zip_
OS_os_
Rotation "Every request"no _s_
Rotation from 1 minute to 1 day_s_ and _ttl_ from 1m to 24h
Session Sticky_s_ without _ttl_
Protocol and formatnot stored in the login

The password changes only through Reset settings → Password. After that, all exported lines stop working.