Nstbrowser proxy setup
Paste one gateway line into a profile's Custom Proxy, or keep lines in a group on the Proxies page. Nstbrowser creates a profile with a proxy only after the proxy passes its check.
- Protocols
- HTTP, HTTPS and SOCKS5 (with a
socks5://prefix), with account and password - UDP
- Not mentioned in Nstbrowser's docs; HTTP on port 7000 is enough for browsing
- Where the setting is
- Custom Proxy in the profile form, or Proxies in the left menu
- Line format
host:port:login:password;socks5://in front for SOCKS5- Works with
- Residential and mobile proxies
Before you start
- The Nstbrowser client installed and signed in.
- Your proxy login and password from Residential or Mobile in the dashboard, with traffic on that product. Without traffic the gateway answers 402 and the profile fails the check.
- Profiles for your own accounts, ads accounts you run for clients with their access, or QA and testing, within each platform's rules.
- Host
gate.aeonproxy.com- Port (HTTP / HTTPS)
7000- Port (SOCKS5)
7001- Login
- your proxy login, with targeting keys if you need them:
LOGIN-cc-us-sid-abc123 - Password
- your proxy password
Copy the login and password from the Residential or Mobile page of the dashboard; the generator there also writes ready lines. Key syntax: targeting and sessions.
Add the proxy to a profile
- Open Profiles and click Create Profile, or edit a profile. Set the name, group, kernel and operating system as usual.
- In the proxy part of the form, choose Custom Proxy, not Local or Platform Proxy (Nstbrowser's own proxy service).
- Paste one line. For HTTP:
gate.aeonproxy.com:7000:LOGIN:PASSWORD. For SOCKS5, with the prefix Nstbrowser asks for:socks5://gate.aeonproxy.com:7001:LOGIN:PASSWORD. Nstbrowser parses the line and fills in the fields. - If the parsed fields show a protocol, it should be HTTP for port 7000, not HTTPS.
- Run the proxy check, then click Create Profile at the bottom left.
Keep lines in a proxy group
- In the dashboard generator, set Session to Sticky (same IP) and Session time to 60 min, generate one line per profile and show them in the
host:port:user:passFormat. For SOCKS5, set Protocol to SOCKS5 and putsocks5://in front of each line. - In Nstbrowser, open Proxies, click Create Group and name it.
- Click Add, paste a line and save. Repeat for the other lines.
- Click Check Proxy. Clear Failed then removes the lines that failed and keeps the rest with their results.
- In each profile, choose Saved Proxies and select a different line.
Do not bind a signed-in profile to Saved Proxy Group. With several lines in the group, Nstbrowser picks one at random each time the profile starts, so the profile gets another session key and another IP.
Check the proxy
Nstbrowser checks a proxy through one of its lookup services (nstbrowser, iplook or ipinfo) and saves the result. It sets the profile's language and time zone from the IP, so confirm the country before you create the profile. After the first start, open the IP checker inside the profile for the IP, location and any WebRTC or DNS leak.
Rotating or sticky
Give each profile one sticky line and keep its targeting. A rotating login changes IP on every connection; keep it for profiles that only read public pages.
gate.aeonproxy.com:7000:LOGIN-cc-us-st-california-sid-nst01-ttl-60:PASSWORD
socks5://gate.aeonproxy.com:7001:LOGIN-cc-us-st-california-sid-nst02-ttl-60:PASSWORDA sticky IP lasts at most 60 minutes (-ttl-60). Then the same line gets a new IP in California, so the language and time zone Nstbrowser picked still fit. There is no way to keep one residential or mobile IP for days.
If it does not work
| What you see | What to check |
|---|---|
| The profile cannot be created | The proxy check failed. 407 means the login, the password or a targeting value outside the dashboard lists; 402 means no traffic left or the sub-user limit. |
| The check hangs on port 7000 | The protocol is HTTPS. Set it to HTTP. |
| A SOCKS5 line fails | The socks5:// prefix is missing, or the port is 7000 instead of 7001. |
| The IP changes at every start | The profile uses Saved Proxy Group with several lines, or a rotating line. Select one sticky line. |
| A profile lost its proxy | Its proxy group was deleted, which deletes the lines in it. Add the line again. |
| 502 | The exit failed. Retry: a rotating line takes another exit, a sticky one keeps its key. |
Questions
Yes. Nstbrowser's endpoint for a profile's proxy takes a URL in scheme://username:password@host:port form, which is our generator's protocol://user:pass@host:port format, for example http://LOGIN:[email protected]:7000. The proxy list API returns such lines with a fresh session key each.
No. Targeting and session go into the login as keys, so one login and password cover every profile; only the -sid- key differs.
Each service uses its own location database, and they sometimes place the same IP in a nearby city.