Proxies
Assign per-profile HTTP, HTTPS, SOCKS5 or SOCKS5H proxies.
VeilBrowser supports assigning a proxy per profile. Traffic for that profile is routed through the configured proxy when the browser launches.
Supported protocols
HTTP
Standard HTTP proxy.
HTTPS
TLS-wrapped HTTP proxy.
SOCKS5
Full TCP tunnelling.
SOCKS5H
SOCKS5 with remote DNS resolution.
Assigning a proxy
Set a proxy when creating or updating a profile. Create body uses ProfileSpec
fields (name, os, browserVersion) — there is no separate profileId on
create:
{
"name": "marketing-us",
"os": "win",
"browserVersion": 131,
"proxy": {
"type": "socks5",
"host": "proxy.example.com",
"port": 1080,
"username": "user",
"password": "secret"
}
}Match the proxy to the identity
Use residential or mobile proxies that match the identity you are presenting. A US profile on a datacenter IP in another country is an easy inconsistency to spot. Timezone, locale and WebRTC alignment to the proxy IP are not applied automatically today — configure those signals to match your proxy when you need them consistent.
Next steps
- Launching — start a profile with its proxy.
- Learn why network signals matter in WebRTC leaks and proxy consistency.