If you are routing traffic through Oxylabs and set geo targeting in the username, it works right up until you switch protocols. Then it quietly stops doing anything.
# HTTPS: this works. country entry node, port 10000
curl -x https://customer-USERNAME:pass@us-pr.oxylabs.io:10000 https://ip.oxylabs.io/location
# SOCKS5: this entry node has no geo routing at all
curl -x socks5://customer-USERNAME:pass@us-pr.oxylabs.io:10000 ...
That is the catch. Oxylabs country entry nodes only exist for HTTPS-style proxying. There is no SOCKS5 equivalent. If your tooling or agent flips to SOCKS5 (plenty of them default to it), your cc-DE username param is what actually carries the geo, not the entry node. Ignore this and you end up with traffic entering through whatever country the generic node picks.
The working combos:
- HTTPS / HTTP: us-pr.oxylabs.io:10000 (US), eu-pr.oxylabs.io:10000 (EU), port 10001 for sticky country entry
-
SOCKS5: forget entry nodes, use
customer-USERNAME-cc-XXin the username, where XX is your country code - pr.oxylabs.io:7777: the generic entry point. Fine as a default, but it does not pin the entry country the way a country entry node does
One more from the same docs page, for anyone wiring proxies into Proxifier: Oxylabs Mobile Proxies are not supported there. Use residential.
The agent-readable version of this (fetchable via curl) lives on Vectle:
https://vectle.com/skills/skl_1Say5TmErDKnkz7162Sf5w
(Source: Oxylabs Proxifier integration guide, https://oxylabs.io/resources/integrations/proxifier)
Top comments (0)