Securing Your Proxy Access
When you purchase premium proxies, you don't want anyone else using your bandwidth. Proxy providers offer two primary methods to authenticate and secure your access: Username & Password (User:Pass) and IP Whitelisting. Here is a breakdown of how they work and which one you should use.
Method 1: Username and Password Authentication
This is the most common method. When configuring your proxy in your software or code, you provide a username and password supplied by your provider.
How it works:
The proxy URL looks like this: http://username:password@proxy-domain.com:port
- Pros: Extremely flexible. You can use your proxies from anywhere—your laptop, a cloud server, or a mobile device—without needing to update your settings. It's ideal for distributed teams or dynamic cloud functions.
- Cons: If your code is exposed (e.g., in a public GitHub repo or a client-side app), someone can steal your credentials and use your bandwidth.
Method 2: IP Whitelisting
With IP whitelisting, you log into your proxy dashboard and authorize your specific server's IP address. The proxy network will then accept any requests originating from that IP without requiring a username or password.
How it works:
You add your server IP (e.g., 198.51.100.14) to the Proxelytics dashboard. Your proxy URL simplifies to: http://proxy-domain.com:port
- Pros: Highly secure. Even if someone finds your proxy endpoint and port, they cannot use it unless they are on your specific server. Your code is cleaner because it doesn't contain hardcoded credentials.
- Cons: Inflexible. If your scraper runs on a home connection with a dynamic IP that changes daily, or on ephemeral cloud functions (like AWS Lambda) where the outbound IP changes constantly, whitelisting becomes a massive headache.
Which Should You Choose?
If you have a dedicated server or VPS with a static IP address running your scrapers 24/7, IP Whitelisting is the safest and cleanest option.
If you run scrapers locally, use cloud functions, or share access with team members, User:Pass is much more practical.
How Proxelytics Handles Authentication
At Proxelytics, we believe in giving developers ultimate control. Our dashboard allows you to use BOTH methods simultaneously. You can generate multiple sub-users with discrete passwords, AND manage a robust list of whitelisted IPs. Read our docs to see how to configure authentication via our REST API, or log in to your dashboard to set it up now.