Proxy and Session
Every connected LinkedIn account runs through its own IP address and its own saved session. Both live on the account row in Settings, on the LinkedIn accounts tab.
The dedicated IP
When you connect a LinkedIn account, SDRPilot sets up a dedicated residential IP address for it before signing in. That address is used only by your account and stays the same, the way your home or office connection would.
This is not optional. LinkedIn treats a well known datacenter address as a red flag, and a sign-in from one is the fastest way to lose a session. SDRPilot refuses to sign in for an account that has no usable IP address yet.
Country matching
During the connect flow you answer Where do you normally use LinkedIn? SDRPilot guesses from your browser, so check it before continuing. The address is bought in that country, and in a city inside it where one is available.
When we already know the location shown on the LinkedIn profile, the city follows it: an address is bought near the city on the profile when the city you picked is far from it or could not be found. It only ever picks a city inside the country the address is bought in.
An account keeps its address. A new address is only bought when the account has none, and a working address is never swapped to match the profile.
If no address is available in the country you asked for, or the addresses there keep failing our quality check, SDRPilot uses the nearest sensible country instead, normally in the same region and within a few hours of your timezone. The account row then shows where the address actually is, so you always know.
If LinkedIn refuses to show its sign-in page on an address, SDRPilot replaces that address with a new one by itself, and the account row asks you to sign in again once it is ready.
If no clean address turns up in your country or the nearby ones, the account row says so. You can connect right away with your own proxy, or try again later.
The row reads something like Runs on a dedicated IP in Amsterdam, the Netherlands. While the address is still being set up it reads Dedicated IP being set up.
Bringing your own proxy
You can use your own proxy instead. Choose Use my own proxy on the account row and enter its details. Your own residential or ISP proxy then replaces the dedicated address this account connects through. Datacenter proxies are rejected.
Use a static residential or ISP proxy, one that keeps the same address for as long as you own it. A rotating proxy changes the address under a signed in session, and LinkedIn treats that like a stolen session and signs the account out. A sticky proxy does the same once its hold time runs out.
You can switch back to a SDRPilot address later. Both changes ask you to confirm first.
An account has to be signed out before its IP address can be changed. A live LinkedIn session cannot move to a new address without looking like a stolen session, so the control is locked while the account is connected and tells you so.
Session health
The session is the sign-in SDRPilot holds for you. It is encrypted at rest and it carries one fixed identity, meaning one browser fingerprint, one timezone and one language, captured at sign-in and reused for everything after it.
On the account row you can:
- check sign-in, to confirm the session is still alive right now
- sign in again, when LinkedIn has ended it
- sign out, to stop all activity on that account without deleting anything
- remove, to delete the account from your workspace. Your agent stays: it keeps running on its other senders, or stops until you give it one.
SDRPilot also checks each healthy account on its own, so a session that dies quietly is noticed rather than discovered days later.
When LinkedIn ends a session, SDRPilot emails the workspace owner once to say which account stopped and that its outreach and replies are paused. The account row shows the same thing, so you can act from whichever you see first.
Connection maintenance
Now and then the network connection behind an account goes down for a while, separate from LinkedIn and from your session. When that happens the account is not signed out and nothing is lost:
- the account row shows a notice, and a short line appears at the top of every page in the app
- the account stays connected, and everything it was going to do (connection requests, messages, replies, searches) waits in the queue
- work picks up automatically as soon as the connection answers again
On an account that runs on a SDRPilot address the notice reads Connection maintenance: our network provider is servicing that account’s connection. There is nothing to do; you do not need to sign in again or change anything.
On an account that uses your own proxy the notice reads Your proxy isn’t responding. The proxy you added is not answering, so check it with your proxy provider. Once it responds, the queued work continues by itself.
Reconnecting
If you ticked Remember my password when connecting, an account whose session is ended tries to sign itself back in once, after a short random delay. It is deliberately cautious:
- it never retries within half an hour of a sign-in that just succeeded
- it stops after two failures in a rolling day, and after four attempts in a rolling day whether they worked or not
- it does not try at all when the last sign-in needed a phone approval or an emailed code and no authenticator secret is saved, because nobody would be there to answer
While automatic reconnecting is in progress the account shows as restricted rather than disconnected. If it cannot finish, sign in again by hand from the same row. You can withdraw the saved password at any time with Forget saved password, and the saved authenticator secret with Forget authenticator key.