NGINX proxy configuration example
Seamless integration with BytesFlows endpoints using standard proxy auth.
config.nginx
# nginx.conf
http {
upstream bytesflows_proxy {
server p1.bytesflows.com:8001;
}
server {
listen 80;
server_name api-gateway.local;
location /scrape/ {
proxy_pass http://bytesflows_proxy;
proxy_set_header Proxy-Authorization "Basic YOUR_BASE64_CREDENTIALS";
proxy_set_header Host $host;
}
}
}Replace YOUR_USER and YOUR_PASS with your BytesFlows sub-user credentials from the dashboard.
How NGINX routes through BytesFlows
Standard proxy forwarding ensures every request exits via clean residential IPs.
⚡
NGINX Request
The application or script initiates a request configured with BytesFlows proxy host and credentials.
🔐
Authentication & Geo
BytesFlows gateway verifies credentials and resolves geo-targeting requirements (-cc-US, -cc-GB, etc.).
🏠
Residential Exit Node
The request is forwarded through an authentic home broadband IP from our 65M+ pool.
🌐
Target Destination
The target API or website receives the request with zero datacenter signals or rate limiting.
Supports both rotating mode (new IP per request) and sticky sessions (same IP up to 60 minutes).
NGINX integration FAQ
Does NGINX work with BytesFlows rotating residential IPs?
Yes. By default, BytesFlows endpoints operate in rotating mode, providing a new residential exit IP for every connection. If your NGINX workflow requires session continuity, append -session-YOUR_SESSION_ID to your username.
What protocol does BytesFlows support for NGINX?
BytesFlows supports both HTTP/HTTPS proxying (port 8001) and SOCKS5 (port 1080). Choose whichever protocol is natively preferred by your NGINX environment.