Session cookie expired" on PhantomBuster: re-auth the session via the browser extension

TL;DR: Make sure the PhantomBuster Chrome/Firefox extension is installed; it is how the tool grabs the cookie. PhantomBuster - Docs (PhantomBuster help center): the official fix for expired/invalid session cookie errors. ## The fix When a Phantom fails with "Session cookie expired" or login errors, do this: 1. In your browser, manually log out of the target site (LinkedIn, X, etc.) and log right back in.

Fix

1. Make sure the PhantomBuster Chrome/Firefox extension is installed; it is how the tool grabs the cookie. Expected: this specific failure stops.

2. Re-run the Phantom. Expected: this specific failure stops.

3. If it keeps failing right after a fresh cookie, check for local interference: aggressive ad-blockers or privacy extensions can break PhantomBuster's page scripts (disable them one by one), and corporate VPNs/firewalls can route traffic through another country, tripping the site's security on a location mismatch with the cookie. Expected: this specific failure stops.

Details

PhantomBuster - Docs (PhantomBuster help center): the official fix for expired/invalid session cookie errors. ## The fix When a Phantom fails with "Session cookie expired" or login errors, do this: 1. In your browser, manually log out of the target site (LinkedIn, X, etc.) and log right back in. 2. 3. On the Phantom's setup page, click the "Connect to..." button and let the extension capture the new active session cookie. 4. Thread: docs:phantombuster-session-cookie-fix

When to use

You hit exactly this: Session cookie expired" on PhantomBuster: re-auth the session via the browser extension in Session.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Session.

In docs:phantombuster-session-cookie-fix (https://support.phantombuster.com/hc/en-us/articles/11034816771090-How-to-Fix-Expired-or-Invalid-Session-Cookie-Errors), the issue reported: Docs (PhantomBuster help center): the official fix for expired/invalid session cookie errors. The affected automation shows a warning icon where the platform identity usually appears, plus an error tag. Click the error to open the Phantom console, click Resolve, and you land on the Setup page with the stale account highlighted; click Re-connect next to it (via the PhantomBuster browser extension or a freshly pasted cookie) and save. The session has to be refreshed from the account owner's side: they reconnect it themselves with the extension, or for shared LinkedIn accounts generate a new magic link. Notes: Slack Phantoms need both a valid cookie and the correct workspace URL (wrong workspace is a common cause), and LinkedIn cookies last roughly 14 days, so a Phantom that degrades gradually is usually a dying session, not a broken Phantom. The verified answer: When a Phantom fails with "Session cookie expired" or login errors, do this:

1. In your browser, manually log out of the target site (LinkedIn, X, etc.) and log right back in.
2. Make sure the PhantomBuster Chrome/Firefox extension is installed; it is how the tool grabs the cookie.
3. On the Phantom's setup page, click the "Connect to..." button and let the extension capture the new active session cookie.
4. Re-run the Phantom.

If it keeps failing right after a fresh cookie, check for local interference: aggressive ad-blockers or privacy extensions can break PhantomBuster's page scripts (disable them one by one), and corporate VPNs/firewalls can route traffic through another country, tripping the site's security on a location mismatch with the cookie.