🌐Proxies FAQ

No. A profile with no proxy uses your own internet connection, and for testing or for keeping two personal accounts apart that's fine.

For anything where the accounts must not look related, you do need one. Without a proxy, every profile you run comes out of the same address — and an address is the single strongest signal that two accounts are the same person. A perfect fingerprint on a shared address doesn't help.

No. There's no proxy store, no bundled traffic and no proxy allowance on any plan. Bring your own from any provider.

The one exception is a phone: you can turn an Android phone into a mobile proxy for your own profiles, free on every plan. See Use an Android phone as a mobile proxy.

Not really. A VPN moves your whole computer onto one address, so every profile you open goes out of the same place — the opposite of what you want. It also can't give each profile a different country.

If you must run LoginDeck behind a VPN, remember that a free LoginDeck account is counted per internet connection, and a shared VPN exit can trip that: "Computer limit reached".

You can, but don't. A proxy set inside the browser leaves the initial connections and WebRTC on your real address, and the profile's timezone won't follow it. LoginDeck sets the proxy at the browser's own level, which is why the clock and language can follow the exit. See WebRTC and IP leaks.

Residential or mobile for consumer platforms and anything that gets challenged. ISP (static residential) when you need one address that never changes. Datacentre only for scraping and tools that don't care — a lot of sites block those ranges outright.

Full comparison: Which proxy should I use?

Technically yes — save it once in Proxies and point as many profiles at it as you like.

Should you? Only for profiles that are allowed to look related. Several accounts on one address is what platforms look for. One proxy per profile is the rule worth following: Good habits that keep accounts safe.

Static for anything you stay logged in to. An account that jumps country between visits looks like account sharing, and a rotating proxy does exactly that.

Rotating is for work where each visit is independent — checking results, gathering data, registrations you don't come back to.

Your provider says so in the dashboard, usually next to the port. Ports are the tell: providers hand out a different port for HTTP and for SOCKS on the same host, so the right host with the wrong port and type behaves exactly like a dead proxy.

If you're not sure, try HTTP first, then SOCKS 5.

No, on any plan.

Paste a provider's line straight into Host and every field fills itself. These all work:

192.168.0.1:8000
socks5://login:password@192.168.0.1:8000
192.168.0.1:8000:login:password
user:pass@2600:1f1e:aa1:ae00:aeaf:8349:7a4d:65b7:1081

Add :name at the end to name it, and put a Change IP link last in square brackets. IPv6 works. There's no SSH proxy support. The full list is in Which proxy should I use?

The line isn't a shape LoginDeck recognises. The other refusals you may see are host is required, port is required, "8oo" is not a port (ports run 1–65535), "192.168.0.1" has no port, and unknown proxy type "ssh" — use http, socks5 or socks4.

Fix the line and press Add proxy again. See Add a proxy.

Import judges every line on its own, so one typo doesn't sink the paste. The sheet reports the line number and reason for each rejected line.

Lines already saved are skipped rather than doubled — matched on type, host, port and login, but not password. So a proxy whose password your provider has rotated reads as "already saved". Edit the existing entry instead. See Import a list of proxies.

Known behaviour of the Add proxy dialog: an https:// line typed into Host on a new proxy sets Type to HTTP. Use Import for HTTPS proxies instead.

Where the proxy really comes out. LoginDeck asks a location service through the proxy, and reports the address, city, country, ISP, timezone and how long the round trip took.

That's the truth, not what you were sold. If you paid for one country and the check says another, take the reported address to your provider. Run it from ⋯ → Check now: Check proxies.

The reason after the dash is the useful half: bad credentials (407), a blocked port, a refused tunnel, a timeout, a dead exit. Each one and its fix is in A proxy won't connect.

Save your provider's rotate link in the proxy's Change IP field, then use the ⇄ button on a profile row to call it. Whether it works, how fast, and how often you're allowed to call it are your provider's rules, not LoginDeck's. See Change a proxy's IP.

Because that's where the proxy is really exiting. Country-targeted and rotating pools drift, and some providers advertise a country the exit doesn't match.

If the exit is right but a website shows the wrong country, check the profile's timezone and language — a browser whose clock disagrees with its address gets read as suspicious. See Timezone and language follow your proxy.

Two different causes. Your provider may only serve certain ports, in which case their dashboard says which. Or something on your side — antivirus, a corporate firewall, your router — blocks the outbound port, which shows up as nothing accepted a connection on that proxy's port.

Test the same proxy from another network to tell the two apart.

Yes — proxies, with their passwords, sync on every plan, encrypted with a key derived from your password. They're also included in profile export files, which is why those files need to be kept private. See What syncs between your computers.

Members of your workspace get the proxies their profiles need, so treat the workspace as a trust boundary. The proxies table never shows passwords on screen — it's the screen most likely to end up in a screenshot. See What members can see and do.

That's deliberate. A profile never falls back to a direct connection, so a deleted proxy stops the launch rather than sending your traffic out on your own address. The Proxy & Location cell reads "🔗 deleted proxy" until you point those profiles somewhere else: Give a profile a proxy.

No. LoginDeck doesn't sell or meter proxy traffic, so there's nothing to share out. Everyone uses whatever proxies the workspace holds, billed by your proxy provider as usual.