A proxy won't connect

When LoginDeck checks a proxy, it asks a location service a question through it. If the answer never comes back, the toast reads "no answer through that proxy — {reason}", and the reason is the useful half.

Run the check from the Proxies page: ⋯ on the row → Check now. See Check proxies and see where they exit.

A failed check does not change the row

If the check never left your machine — you are offline — the row keeps its last real result and only the toast reports. A proxy that was never tested is not marked dead.

🔑 "the proxy rejected the credentials (407)"#

The username or password is wrong, or the proxy expects a different one.

⋯ → Edit on the proxy.
Retype Login and Password from your provider's dashboard. The eye button shows the password so you can compare it.
Check the login format your provider wants. Many residential providers put the country or session in the username (user-country-us), and a stale session string reads as a bad password.
Some providers authenticate by IP allowlist instead of a username. If yours does, add your current address in their dashboard and clear both fields here.

🚪 "nothing accepted a connection on that proxy's port — it may be blocked on this machine or by the network"#

The address answered nothing at all on that port.

Check the port. Providers hand out different ports for HTTP and SOCKS on the same host, and a port copied from the wrong column fails exactly like this.
Check the Type. HTTP, SOCKS 5 and SOCKS 4 are not interchangeable — the right host and port with the wrong type behaves like a dead proxy.
Try the same proxy from another program or another network. If it fails everywhere, it is the proxy.
If it works elsewhere but not here, your antivirus, VPN client or corporate firewall is blocking the outbound port.

🕳️ "the proxy's hostname would not resolve"#

Your computer could not turn the proxy's hostname into an address. Usually a typo in the host, an expired gateway hostname, or a DNS problem on your own connection. Copy the host again from your provider.

Its close relative, "the lookup host would not resolve through that proxy", means the proxy connected but could not resolve anything for you — common on proxies that only allow certain destinations.

🚧 "the proxy refused to open the tunnel" / "the proxy refused to open a tunnel (405)"#

The proxy is alive and said no. Almost always one of:

your plan with that provider has run out of traffic or expired
your current IP is not on the provider's allowlist
the proxy is HTTP-only and won't carry HTTPS traffic, which every site now needs
you picked SOCKS 5 for an HTTP proxy, or the reverse

Check the plan and the allowlist in your provider's dashboard first.

⏳ "it timed out after 20s"#

Nothing came back in time. LoginDeck waits 20 seconds through a proxy and 10 seconds without one.

Mobile and residential proxies are genuinely slow to start. Check again once before believing it.
A proxy that times out every time on a good connection is overloaded or dead. Rotate its IP if your provider supports it (Change a proxy's IP), or ask them for a replacement.
Very high latency is also worth acting on. The Speed column in the Proxies list is how long that round trip took.

✂️ Other reasons, in one table#

Reason	What it means
the TLS handshake through that proxy failed	The tunnel opened, then encryption failed. Often a proxy that tries to inspect traffic, or the wrong Type.
the proxy accepted the connection and then said nothing	It connected and hung up without answering. Usually an overloaded gateway.
the connection through the proxy was cut	Dropped mid-answer. Retry; if it repeats, the exit is unstable.
no internet connection — this machine cannot reach anything even without the proxy	Your own connection is down. Nothing is wrong with the proxy.
the lookup answered without an address / neither lookup answered	Something answered, but not the location service. A captive portal or a filtering proxy usually does this.
the answer was not what a lookup returns ("…")	The quoted text is what came back — often a provider's error page or a login portal. Read it; it usually says what is wrong.
curl is missing from this machine — LoginDeck uses it for the lookup	`curl` has been removed from Windows. Restore it, or repair Windows.

🧭 It connects, but exits in the wrong country#

Not a connection problem. The check reports the address, city, country, ISP and timezone it actually found, and that is the truth — not what you were sold.

On a rotating or country-targeted proxy, the exit moves. Re-check to see where it is now.
If you paid for a specific country and the check says elsewhere, take the reported address to your provider.
A profile whose timezone is set to Match the exit IP follows whatever the check found. See Timezone and language follow your proxy.

🚀 The proxy is fine, but a profile won't launch#

A profile never falls back to a direct connection, so a broken proxy stops the launch instead of leaking your own address. Those messages are covered in A profile won't start.

If a launch succeeds but a red toast says the profile "opened on its stored clock", the check through the proxy failed during launch. The browser is running on the timezone saved on the profile, which checkers will flag. Stop it, fix the proxy, launch again.

🌍 One site won't open, the rest work#

That is the site, not the proxy. Datacentre ranges are blocked wholesale by many sites, and a residential address that has been abused before arrives with a reputation. Try a different exit, and read What no antidetect browser can change.

ℹ️ If it still won't connect#

Confirm the proxy works outside LoginDeck first — that tells you which side to chase. Then email support@logindeck.com with:

the exact reason text from the toast
the proxy Type, and whether it needs a login (never send the password)
the provider's name and what they advertise the proxy as
whether the same proxy works in another program on the same computer

See Contact support.