Linken Sphere proxy setup

Protocols

SOCKS5 and HTTP(S), with login and password

UDP

Over SOCKS5, per Linken Sphere's blog (December 2025): WebRTC, QUIC and WebTransport. Its docs say the HTTP type does not proxy WebRTC

Where the setting is

New Session → Connection, a preset's Connection block, or the Proxy Manager

Works with

Residential and mobile proxies

Before you start

• Linken Sphere 2 installed.
• 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.
• One session per account: your own, or a client's account you manage with their access, used within the platform's rules.

Set the proxy in a new session

1. Select New Session and fill in the General block.
2. In the Connection block choose Socks5.
3. Paste a generator line with port 7001. Linken Sphere reads all four plain layouts the generator writes: host:port:user:pass, host:port@user:pass, user:pass:host:port and user:pass@host:port.
4. Select Check proxy and geo. It shows the IP, country, language and time zone, and the session takes its language, time zone and geolocation from that IP.
5. Keep WebRTC on Adaptive and, in the Miscellaneous block, QUIC support on. Both are the defaults.
6. Select Create, or Create and launch.

For an existing session, paste a line straight into its Proxy column, or open the three dots → Set proxy. Quick paste in the Actions column takes several lines at once and links them to the selected sessions; Linken Sphere detects the type and checks each line.

Many sessions: Proxy Manager and presets

1. Open the Proxy Manager with the Proxy icon at the top right and select Import from list.
2. Choose SOCKS5 as the protocol, give the group a name such as US Texas, and paste the lines. Each one is checked for IP, country and ZIP code.
3. Create a preset, open its Connection block, tick the proxies in the Proxy Manager list (ones already in use are marked red) and select Set.
4. Create sessions from that preset in bulk: each new session takes its own line from the Proxy Manager.

Check the proxy

Check proxy and geo uses the MaxMind database. For a session that already exists, the Check proxy action in the session manager tests the line again. To see the result the way a site does, open the IP checker in the session: on a SOCKS5 line its WebRTC test should show the proxy's IP, not yours.

Rotating or sticky

Use one sticky line per session (in the generator: Sticky (same IP), Session time 60 min). Every connection with the same -sid- key, UDP included, leaves from one IP for up to 60 minutes (-ttl-60), then the line gets a new IP from the same targeting. No setting holds a residential or mobile IP for days, so give every line of a group the same targeting.

LOGIN-cc-gb-st-scotland-sid-ls000017-ttl-60

If a session stays open longer than its sticky time, turn on Live mode for its SOCKS5 connection. Linken Sphere then keeps WebRTC, language, geolocation and time zone in line with the current IP when it changes during the session.

If it does not work