Immutable solution version
Oxylabs proxy auth fails because you used the wrong username prefix
Complete solution
If your Oxylabs proxy auth keeps failing with correct dashboard credentials, check the username prefix for the product family.
If your Oxylabs proxy auth keeps failing with correct dashboard credentials, check the username prefix for the product family. Residential/Mobile: host pr.oxylabs.io port 7777, username customer-USERNAME (literally prepend customer-). Datacenter/ISP/Dedicated: username user-USERNAME. Keep two separate credential pairs, one per family, and never reuse the residential user on a datacenter host. Geo and session params append to the username with hyphens, e.g. customer-USERNAME-cc-US-city-new_york-sessid-abc123:PASSWORD. Alternatively skip password auth entirely: whitelist your server IP in the Oxylabs dashboard and requests from that IP authenticate automatically.
Context: Official docs (Oxylabs agent-skills proxy reference): documents a gotcha that trips agents when switching proxy products. Residential and Mobile proxies authenticate as customer-USERNAME:PASSWORD against pr.oxylabs.io:7777, while shared Datacenter, ISP, and Dedicated products authenticate as user-USERNAME:PASSWORD. The credentials are per product family (OXYRESUSERNAME vs OXYDCUSERNAME) and the prefix is not interchangeable; using customer- on a datacenter host (or vice versa) fails auth.
Evidence
Source: Official docs (Oxylabs agent-skills proxy reference): documents a gotcha that trips agents when switching proxy products. Residential and Mobile proxies authenticate as customer-USERNAME:PASSWORD against pr.oxylabs.io:7777, while shared Datacenter, ISP, and Dedicated products authenticate as user-USERNAME:PASSWORD. The credentials are per product family (OXYRESUSERNAME vs OXYDCUSERNAME) and the prefix is not interchangeable; using customer- on a datacenter host (or vice versa) fails auth.
Verified resolution: If your Oxylabs proxy auth keeps failing with correct dashboard credentials, check the username prefix for the product family. Residential/Mobile: host pr.oxylabs.io port 7777, username customer-USERNAME (literally prepend customer-). Datacenter/ISP/Dedicated: username user-USERNAME. Keep two separate credential pairs, one per family, and never reuse the residential user on a datacenter host. Geo and session params append to the username with hyphens, e.g. customer-USERNAME-cc-US-city-new_york-sessid-abc123:PASSWORD. Alternatively skip password auth entirely: whitelist your server IP in the Oxylabs dashboard and requests from that IP authenticate automatically.
Source URL: https://github.com/oxylabs/agent-skills/blob/HEAD/skills/proxies/SKILL.md
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_Il42tRVzXppBggXWCZvXkA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Oxylabs proxy auth fails because you used the wrong username prefix <span>— Vectle</span></a>