Is this even broken?
Idle browsers power off after 15 minutes without activity and wake on the next due sync or action, and recurring syncs only start inside the account’s sync window. The power-off and a closed sync window write nothing to the browser event log; the wake writes astarted_by_user row, Starting by user: system.
Check 1: read the two statuses
The browser and the proxy carry separate statuses, and a dead proxy does not show up as a proxy-named browser status. Read both on the Browser tab of the account drawer (Senders, click the row): the proxy block shows residential or datacenter, country, latency and a Proxy uptime row. Hover the Proxy uptime row to readProxy status: active | no connection | fraud flagged | replaced. When the managed proxy now exits in a country other than the one chosen
for the browser, the drawer says so at the top, The proxy’s country changed, with a Change
proxy button (Check 4).
Only two browser statuses point at the proxy: running issue, a runtime fault and where a
proxy failure lands, and start issue, frequently a proxy that timed out. login issue is a
lost session (Check 6); idle is auto-suspend; subscription required is billing; shared
out leaves the proxy with the owning team (full list).
Check 2: read the event log
Scroll to Browser event log at the bottom of the same tab, or search it atPOST /api/antidetect-browser-logs/search. Match what you see against the exact strings:
The
666, -3, -2 and 5xx rows all land as runtime_error: the numeric Code is the only
axis that tells them apart, so filter on code, not on a finer event_type.
If the newest entry is proxy_replaced with Proxy replaced after failure, the platform already
moved the browser onto a healthy proxy but did not restart it: use Start in the row menu.
Check 3: run the connectivity check
This is the answer to “is the proxy actually dead”. It performs a real HTTPS request through the proxy and times it. Take the proxy sid (ab_px_...) off the browser row by searching
antidetect-browsers with "include": ["antidetect_browser_proxy"]. This check and the location
one run over the API and MCP only, with no button in the app, and both require the
can_change_proxy permission: a member without it gets a 403.
curl
total_checked, ok, avg_connection_time_ms (the mean over the rows that
answered, null when none did) and failed[], where each entry has an error_kind:
Send exactly one of
sid or filter. Both or neither returns 422 with
field_errors.sid_or_filter set to Provide exactly one of sid or filter. In filter mode a
single call probes at most 50 rows; the response reports the true match count in
total_matched and sets truncated: true when the cap was hit.
Check 4: run the location check
Run this when the account keeps hitting verification challenges rather than failing to load. Start with the browser itself: on a browser read,proxy_actual_country_code is the country its
managed proxy exits in, as LinkedIn last saw it, and proxy_country_code is the country chosen
for the browser. When the two differ, LinkedIn sees the sender somewhere other than where you
chose, and the fix is a swap back into your country (Check 5).
The location check asks several geo vendors and several fraud databases about the exit IP right
now. Same request as above with the endpoint swapped for check-proxy-location, same sid or
filter rule, same 50-row cap. It reports two things:
- The exit country. The verdict is the real exit country, measured through the proxy, not a
vote among IP databases. A proxy whose exit disagrees with its country is listed in
country_mismatched, and that is all: the check never changes a proxy’s country or status. Only a LinkedIn session seen through the proxy moves its country, because what LinkedIn shows outranks the geo vendors. Thedisagreement_pctis context only. - Fraud flag. The aggregated score is the highest score any responding database returned.
total_checked.
Check 5: swap the proxy
Two different operations, one dialog. On Senders, open the account’s row menu, click Change proxy, pick a mode and confirm.
Rotating is the safe default. The country dropdown lists only countries that currently have an
active proxy in the pool, and blocks the country the browser is already in.
What each swap restarts
Both verbs stop the live session, push the new upstream into the profile, commit, then start the browser again. A running browser keeps egressing through the old proxy until it respawns.
The response carries
restarted: true|false and restart_error, the literal string
restart_failed when the browser could not come back up. In the app that shows the toast “The
proxy was changed, but the browser could not be started again. Start it from the row menu.” The
swap itself still committed.
Swap refusals
Switch onerror.field_errors for 422 and on error.context.reason for 409 and 503: the
top-level error.code is only validation_failed, conflict or service_unavailable.
Only a profile gtm-api minted takes a proxy change here. A profile you bound by its id keeps its
proxy in the GoLogin account that holds it, whoever that is: the menu item is disabled, with the
reason on hover, and the dialog is never offered. Change the proxy in the GoLogin app, then
Restart the browser.
Check 6: if it is the session, not the proxy
A browser in login issue is not a network problem. LinkedIn invalidated the session, the status is sticky, and no proxy swap, restart or wait will clear it. During the initial sync the drawer shows Sync paused, action needed with the reasonbrowser:logged_out; after the initial sync
it shows Signed out of LinkedIn with a Log in via cloud browser button. Re-login is the
only fix, in the app or through
Generate re-login link for the account’s owner (how).
Meanwhile a sync run parked on a broken browser re-checks every 30 minutes and holds its place
in the queue, and a run waiting on an idle browser to cold-start re-checks every 60 seconds.
Only running and idle browsers are woken by a sync run itself. A browser in running_issue or
start_issue is restarted by the platform every ten minutes until it either runs or is parked. A
parked browser (client_error_investigation, support_error_investigation) is tried again on its
own when the cause is one a retry can outlive: every three hours when the fault is on our side,
and, when it is the proxy inside your profile, after three hours, then six, then twelve, then
once a day for two weeks. A parking on any other cause of yours (the session, a deleted profile,
the account connected in another workspace), a login_issue and a maintenance wait for an
explicit start.
What the platform already does on its own
- Every active proxy is probed every 5 minutes, and one that fails is probed again every
minute. It turns
no_connectonly after five failed probes in a row, so a blip of a minute or two leaves it and your browsers alone, and it isactiveagain on the first probe that goes through. When most of the proxies probed in one minute fail at once, the fault is on the path, not in the proxies, and nothing is changed. Flagged and replaced proxies are not probed. Fraud is re-checked weekly, 100 active proxies per run. No geo check runs on a schedule: a proxy’s country follows only what LinkedIn shows. - A browser keeps the country chosen for it. When a LinkedIn session seen through a proxy
shows another country, the proxy is registered in that country and the browser on it keeps
yours, so the next swap or rotation picks a proxy in your country again. Until then the browser’s
proxy_actual_country_codenames the new country and the account drawer shows The proxy’s country changed. The proxy stays in service either way. - A browser that reports a proxy error is rotated automatically, but never restarted (Check 2).
- Integrations get told by the
antidetect-browsers.proxy-issueandantidetect-browsers.proxy-back-alivewebhook events, both carryingantidetect_browser_proxy_sid: one when a proxy turnsno_connect, one when it is back. There is no separate proxy-level webhook.
When to contact support
A ticket resolves in one round trip when it carries the account name, a screenshot of the drawer’s
Browser tab showing both statuses, the literal
Code and Message of the newest error row in
the event log, and the raw JSON of any 422, 409 or 503 a swap returned. Request shapes for
every endpoint above are in the API reference.