SessionBox Mobile Proxies for Social Accounts

SessionBox is a lightweight way to run several logged-in sessions of the same site in one browser. Each session keeps its own cookies and storage, so a community manager can hold a handful of social accounts open in separate tabs without constantly signing in and out. On its own, though, every session leaves through the same connection. Assigning a mobile proxy to each session fixes that, and ProxySocial provides USA carrier addresses from real SIM cards on AT&T, T-Mobile and Verizon to do it with. This guide explains how the two fit together and how to keep social sessions stable.

How SessionBox isolates sessions and where proxies fit

SessionBox comes as a browser extension and as a standalone application, and the standalone version adds a fuller set of tools, including per-session proxy settings. A session is a container with its own cookie jar; opening a site inside it gives you an independent login. When a proxy is attached to the session, the requests from that container leave through the proxy instead of your normal connection.

The proxy fields are the familiar set: a type such as HTTP or SOCKS5, a host, a port, and a username and password. The exact layout depends on which version of SessionBox you run, so look for the proxy area within the session's settings rather than a global option. If your edition does not offer per-session proxies, a system-level proxy still routes every session through one ProxySocial address, which is fine for a single account but not for several.

Gathering details from ProxySocial

In the ProxySocial dashboard each proxy is listed with its host, an HTTP port, a SOCKS5 port, a username, a password and a rotation link. For SessionBox you need the host, one port and the credentials. Keep the rotation link out of the browser; it belongs in the dashboard or in a script that runs between sessions.

For social browsing HTTP is enough and is the simplest to configure. SOCKS5 is worth choosing if the session will use web-based calling or live video that relies on UDP, which our SOCKS5 endpoint supports.

Step-by-step: proxying a SessionBox session

Set up one session first, confirm it works, then repeat for the rest.

• Create a session in SessionBox and open its settings.
• Find the proxy area and select the type that matches the port you copied from ProxySocial.
• Enter the host, port, username and password.
• If a test or check option is offered, run it; otherwise open a public IP lookup page inside the session and confirm it shows a US carrier address.
• Check that the reported city matches the metro of your proxy before signing into any account.
• Name the session after the account and the proxy's metro so you can tell them apart at a glance.

Sticky sessions are the rule for social accounts

A social account that is signed in should stay on one IP for the whole visit. ProxySocial proxies are sticky by default and only change address when you trigger a rotation, so a SessionBox session will keep the same carrier IP from the moment you open it until you close it.

When you do want a new address, close the session, use the rotation link or the API, and reopen it. Rotations are unlimited on every plan. Never rotate while a session is active; the account will see its network route change mid-visit and may ask you to verify. Per-request rotation exists for monitoring and research tasks but has no place in a logged-in social session.

Managing several accounts and cities

Use one proxy per session. Sharing one address among several social accounts ties them together at the network level, which is the opposite of what session isolation is for. SessionBox lets you name and organise sessions, so encode the metro and carrier in each name and keep a simple sheet mapping sessions to ProxySocial proxies.

Our hardware sits in eight US metros, including New York, Los Angeles, Chicago, Houston, Phoenix, Miami and North Carolina on 4G and 5G, plus Boston on 4G LTE. Pick a metro that matches where the account claims to be. If you need to relocate an account's proxy later, location moves are free — just ask.

SessionBox is deliberately simple and does not try to be a full automation platform, so most customers keep the workflow manual: open the session, do the day's engagement, close it. Where you do automate, use the ProxySocial API to rotate proxies between working hours rather than during them.

Troubleshooting

These cover almost every issue we hear about.

• Session will not load pages: the port and the type disagree, or the credentials have a stray space. Re-copy them from ProxySocial.
• IP lookup shows your home address: the proxy is not attached to that session, or the edition in use lacks per-session proxies. Confirm the setting is on the session itself.
• Location on the site differs from the proxy metro: the browser's own timezone is being read. SessionBox does not spoof fingerprints, so set the operating system timezone to match the metro, or use an anti-detect browser if you need full fingerprint control.
• WebRTC reveals a local address: disable WebRTC in the browser or use an extension that masks it.
• Uploads are slow: our 4G typically delivers 20–45 Mbps and 5G 50+ Mbps, so a slow stretch is normally a busy tower. Rotating between sessions usually clears it.

Why ProxySocial mobile IPs

Social platforms are built for phones, and their trust models are tuned to carrier networks. ProxySocial proxies come from real SIM cards on AT&T, T-Mobile and Verizon in modems we own, with HTTP(S) and SOCKS5 with UDP, sticky or per-request rotation, a per-proxy rotation link and an API. Every plan includes 15 GB of data per day, which is far more than a day of engagement across a handful of sessions needs, and plans run daily, weekly or monthly from $5 per day.

Frequently asked