Rayobyte Authentication Options: Username and Password or IP Whitelisting

Two ways to prove it's you

A proxy has to know you're a paying customer. Rayobyte supports the two standard methods:

1. Username and password. You send credentials with each connection. Works from anywhere.
2. IP whitelisting. You register your server's public IP in the dashboard. Connections from that IP are accepted with no credentials.

On static ISP and datacenter proxies, Rayobyte says both methods work on every IP. On rotating products, the username usually carries extra parameters such as targeting and session settings. Our proxy authentication methods guide explains the general picture.

When to use username and password

• Your IP changes, such as on a laptop, a home connection or serverless functions.
• You want targeting or sessions encoded in the username on rotating products.
• Several people or services share an account and you want separate proxy users.
• Your tool supports credentials, which almost all scraping libraries do.

When to use IP whitelisting

• Browsers with SOCKS5. Chromium doesn't support SOCKS5 with a username and password, so whitelisting is the clean workaround.
• Tools that can't send proxy credentials, such as some desktop apps and older software.
• Servers with fixed IPs, where whitelisting is simpler and keeps passwords out of config files.
• Antidetect browsers that struggle with credentials on some proxy types. See Rayobyte with antidetect browsers.

Formats you'll see

The dashboard's generator gives proxy details in the formats tools expect:

host:port:username:password
http://username:password@host:port
socks5h://username:password@host:port

With whitelisting, drop the credentials: http://host:port.

Authentication in common tools

• Python Requests: put the credentials in the proxy URL. See Rayobyte with Python.
• Puppeteer and Playwright: pass the server in launch options and credentials via page.authenticate() in Puppeteer or the proxy object in Playwright. See Rayobyte with Puppeteer and our guide to Puppeteer proxy authentication.
• Selenium: Chrome can't take proxy credentials on the command line, so use whitelisting, an extension, or a helper such as Selenium Wire. See Rayobyte with Selenium.
• cURL: curl -x http://user:pass@host:port https://example.com.

Security habits

• Keep credentials in environment variables, not in code or screenshots.
• Use separate proxy users for separate projects, so you can revoke one without breaking the rest.
• Prune your whitelist. Old server IPs on a whitelist are an open door if someone else gets that IP.
• Rotate passwords when someone leaves the team.

Fixing 407 errors

HTTP 407 means "proxy authentication required". Check, in order:

1. Credentials copied exactly, with no trailing spaces.
2. Special characters in the password URL-encoded in proxy URLs.
3. The right host and port for the product and protocol.
4. Your current public IP on the whitelist, if you're relying on whitelisting.
5. A browser trying SOCKS5 with credentials (unsupported in Chromium).

More fixes in Rayobyte troubleshooting.

How it compares

Geonode and Webshare both support username and password and IP whitelisting (Webshare calls it IP authorization). The practical differences are in how parameters are encoded and how many whitelist entries you get. See Rayobyte vs Geonode authentication, Rayobyte vs Webshare authentication and all three compared.

Before you commit to any provider, it helps to see the wider market: our guide to the best proxies in 2026 compares proxy types by job, and cheap proxies explains how to keep costs down without buying IPs that get blocked.

Key takeaways

• Rayobyte supports username and password and IP whitelisting; both work on every static IP.
• Use credentials when your IP changes or you need targeting parameters; whitelisting for browsers with SOCKS5 and fixed servers.
• Keep credentials out of code and prune your whitelist.
• 407 errors are almost always credentials, encoding, port or whitelist mistakes.

FAQ

Can I use both methods at once?

Yes. Whitelisted servers can connect without credentials while other machines use username and password.

Why does my browser ignore the proxy password?

Chromium-based browsers don't support credentials on SOCKS5 proxies. Use HTTP, or whitelist your IP.

Where do I add whitelisted IPs?

In the Rayobyte dashboard, in the authentication or whitelist settings for your proxies.