Proxy Management

Proxies are intermediary servers that route your internet traffic through a different IP address. When you use a proxy, the website you’re scraping sees the proxy’s IP address instead of your real one. This makes it much harder for websites to detect and block your automation.

RTILA X includes a built-in proxy management system that handles proxy rotation, failure detection, and automatic failover — all without any manual intervention during your automation runs.

Configuring Proxies

Where to Configure

You can configure proxies in two places:

Location	Scope
Preferences → Stealth & Proxies	Global defaults for all projects
Browser Profiles	Per-project settings that override global defaults

Proxy Format

RTILA X supports two proxy formats:

Standard Format (Recommended)

scheme://username:password@host:port

Examples:

http://user1:pass1@192.168.1.100:8080
http://user2:pass2@proxy.example.com:3128
https://user3:pass3@proxy.provider.net:8443

Legacy Format (Auto-Converted)

scheme://host:port:username:password

Examples:

http://192.168.1.100:8080:user1:pass1
http://proxy.example.com:3128:user2:pass2

Note: The legacy format is automatically converted to the standard format internally. You can use either format, but the standard format is recommended for clarity.

Supported Proxy Types

Type	Supported	Notes
HTTP	✅ Yes	Most common proxy type
HTTPS	✅ Yes	Secure proxy connection
SOCKS4	❌ No	Not supported
SOCKS5	❌ No	Not supported

Important: RTILA X only supports HTTP and HTTPS proxies. SOCKS proxies are not supported. If your proxy provider only offers SOCKS proxies, you’ll need to find an HTTP/HTTPS alternative.

Entering Proxies

Enter one proxy per line in the Proxy List field:

http://user1:pass1@proxy1.example.com:8080
http://user2:pass2@proxy2.example.com:8080
http://user3:pass3@proxy3.example.com:8080

Tip: You can enter as many proxies as you need. RTILA X will rotate through them automatically. More proxies means better IP distribution and lower chance of detection.

Proxy Levels

RTILA X offers two proxy levels that control how proxies are applied:

Level	Description	Best For
Context Level (Recommended)	Each browser session (context) gets its own proxy. Different tabs or pages can use different proxies.	Most use cases. Provides better IP distribution.
Browser Level	All browser sessions share the same proxy. The proxy is applied at the browser level.	Simple setups where you only need one proxy.

Context Level (Recommended)

With Context Level, each browser context (essentially each “session” or “tab group”) gets its own proxy from your list. This means:

• Different pages can appear to come from different IPs.
• If one proxy fails, only that session is affected.
• Better IP distribution across your automation.

Browser Level

With Browser Level, the proxy is applied to the entire browser. All pages and sessions use the same proxy. This is simpler but provides less IP diversity.

Tip: Use Context Level unless you have a specific reason to use Browser Level. Context Level provides better stealth and resilience.

Proxy Rotation Mechanism

RTILA X’s ProxyManager handles proxy rotation automatically:

1. Sequential rotation: Proxies are used in the order they appear in your list. The first proxy is used for the first request, the second proxy for the second request, and so on. When the end of the list is reached, rotation starts over from the beginning.

2. Automatic failover: If a proxy fails (connection error, timeout, authentication failure), it’s automatically marked as “dead” and skipped. The next proxy in the list is used instead.

3. Quarantine reset: If all proxies are marked as dead, the quarantine list is automatically reset and rotation starts over. This prevents your automation from getting stuck when all proxies temporarily fail.

Rotation Flow

Request 1 → Proxy 1 (success)
Request 2 → Proxy 2 (success)
Request 3 → Proxy 3 (fails) → marked as dead
Request 4 → Proxy 4 (success)
Request 5 → Proxy 1 (success)
...
All proxies dead → quarantine reset → start over from Proxy 1

Dead Proxy Quarantine

When a proxy fails, RTILA X marks it as “dead” and adds it to a quarantine list. Dead proxies are skipped during rotation.

What Causes a Proxy to Be Marked as Dead

Failure Type	Description
Connection error	The proxy server is unreachable
Timeout	The proxy didn’t respond within the time limit
Authentication failure	The proxy rejected the username/password
DNS resolution failure	The proxy hostname couldn’t be resolved

Quarantine Reset

If all proxies in your list are marked as dead, RTILA X automatically resets the quarantine list. This means:

• All proxies are marked as “alive” again.
• Rotation starts over from the first proxy.
• This prevents your automation from getting permanently stuck.

Note: The quarantine reset is a safety mechanism. If your proxies are genuinely dead (e.g., your proxy subscription expired), the reset won’t help. You’ll need to update your proxy list.

Testing Proxies

Before running your automation, you can test your proxies to make sure they’re working:

1. Go to Preferences → Stealth & Proxies.
2. Enter your proxy list.
3. Click the Test Proxies button.
4. RTILA X connects to each proxy and makes a test request.
5. Results show how many proxies are working vs. failed.

Test Results

Result	Meaning
All X proxies are working successfully!	All proxies passed the test. You’re good to go.
Tested X proxies: Y working, Z failed. Last error: …	Some proxies failed. Check the error message and fix the failing proxies.

What the Test Does

1. RTILA X connects to each proxy via TCP.
2. It makes a test HTTP request through the proxy.
3. It verifies the response comes from a different IP than your real IP.
4. If the response IP matches your real IP, the proxy is flagged as “bypassed” (not actually routing traffic).

Tip: Always test your proxies before running a long automation. A single bad proxy can cause your entire run to fail.

Proxy Tips

Tip	Why It Matters
Use residential proxies for best results	Residential proxies use real home IPs and are much harder to detect than datacenter proxies.
Use different IPs per session	Use Context Level proxy mode for better IP distribution.
Always enable Fingerprint Alignment	Matching timezone/locale to proxy location prevents a common detection method.
Test proxies before running	A single bad proxy can cause your entire run to fail.
Use more proxies for large scrapes	More proxies means better IP distribution and lower detection risk.
Monitor proxy health	If your automation starts failing, check if your proxies are still working.
Avoid free proxies	Free proxies are unreliable, slow, and often already flagged by websites.
Rotate proxies regularly	If you’re scraping the same site frequently, rotate your proxy list to avoid IP-based blocking.
Use HTTPS proxies when possible	HTTPS proxies encrypt your traffic, adding an extra layer of privacy.
Don’t overload proxies	Sending too many requests through one proxy can get it blocked. Use multiple proxies for high-volume scraping.