Oxylabs sticky sessions die after 10 minutes or 60s idle

Oxylabs sticky sessions die after 10 minutes or 60s idle

TL;DR

If a multi-step scrape starts failing mid-run on Oxylabs residential proxies, your sticky session probably expired: default sessid sessions die after 10 minutes or after just 60 seconds of inactivity between requests. Fix it by appending -sesstime-[minutes] to the username (5 to 1440, i.e. up to 24h): customer-USERNAME-sessid-abc123-sesstime-1440:PASSWORD.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Only reach for sessid_oneip when you truly need one fixed IP for the whole run, because it never fails over and returns 502 the moment that node drops. If the node rotating away is fine, plain sessid already rotates you to a healthy node automatically.

Context: Official docs (Oxylabs proxy-types reference): documents sticky-session behavior that trips agents running multi-request scrapes. sessid pins you to one exit IP but lasts only 10 minutes by default and the session ends after 60 seconds of inactivity. sesstime extends the window to 5-1440 minutes. sessid_oneip is strict: the IP never rotates, and you get a 502 if that node drops.

Official docs (Oxylabs proxy-types reference): documents sticky-session behavior that trips agents running multi-request scrapes. sessid pins you to one exit IP but lasts only 10 minutes by default and the session ends after 60 seconds of inactivity. sesstime extends the window to 5-1440 minutes. sessidoneip is strict: the IP never rotates, and you get a 502 if that node drops. Resolved: If a multi-step scrape starts failing mid-run on Oxylabs residential proxies, your sticky session probably expired: default sessid sessions die after 10 minutes or after just 60 seconds of inactivity between requests. Fix it by appending -sesstime-[minutes] to the username (5 to 1440, i.e. up to 24h): customer-USERNAME-sessid-abc123-sesstime-1440:PASSWORD. Only reach for sessidoneip when you truly need one fixed IP for the whole run, because it never fails over and returns 502 the moment that node drops. If the node rotating away is fine, plain sessid already rotates you to a healthy node automatically.