Vision proxy setup

Protocols

HTTP/HTTPS, SOCKS4 and SOCKS5; use SOCKS5 or HTTP, both with login and password

UDP

Vision says it routes all traffic, UDP included, through the proxy; on our gateway that takes SOCKS5 (port 7001)

Where the setting is

Folder → Proxies tab → Create proxy, or Create profile → Add proxy

Works with

Residential and mobile proxies

Before you start

• Pick the folder first. Vision keeps proxies per folder: lines added in one folder do not show up in another, though you can transfer them.
• Your proxy login and password from the Residential or Mobile page of the dashboard, and traffic on that product: a login without traffic gets 402.
• A profile per account you run, yours or a client's that you manage with their access, used within each platform's rules.

Add a proxy while creating a profile

1. In the folder, select Create profile and name it. Of the three proxy buttons, choose Add proxy.
2. Select SOCKS5.
3. Copy a line from the dashboard generator (Protocol SOCKS5, Session time 60 min, format host:port:user:pass) and paste it into the Proxy field.
4. Leave the IP change link empty (our lines change IP through the session key) and name the proxy if you like.
5. Finish the profile with Create profile.

For an existing profile, select the + (or the current proxy's name) in the Proxy column of the Profiles tab, then Add proxy, or Select proxy to reuse one saved in the folder.

Add many lines: Mass Proxy Creation

1. Open the folder's Proxies tab, select Create proxy, then the Mass Proxy Creation tab.
2. Generate lines with Protocol SOCKS5 and the format protocol://user:pass@host:port. Each line starts with socks5://, so Vision takes the type from the line.
3. Paste them, or drag a .txt file onto the form. Check the preview (Type, Host, Port, Login, Password) and select Create.

socks5://LOGIN-cc-us-st-california-sid-vs000003-ttl-60:[email protected]:7001

The Profiles column of the Proxies tab counts how many profiles use each proxy. Keep it at 1, so no two profiles share an IP.

Check the proxy

Start the profile and open the IP checker. It shows the IP and location a site sees and runs a WebRTC test. On a SOCKS5 line the WebRTC address should be the proxy's IP, since Vision routes UDP through the proxy. An HTTP line cannot carry UDP, so WebRTC then depends on the profile's own WebRTC setting rather than the proxy. To test lines before you add them, paste them into the proxy tester.

Rotating or sticky

Use one sticky line per profile. Over SOCKS5 a profile opens several connections, TCP for pages and UDP for WebRTC. With a rotating login each of them can leave from a different IP, and a site would see the page and the call come from different addresses. With a -sid- key they share one IP for up to 60 minutes; then the line moves to a new IP with the same targeting. No residential or mobile IP stays for days, so keep the place stable: the same country, region or city on every line a profile uses.

LOGIN-cc-us-st-california-sid-vs000004-ttl-60

If it does not work