FlareProx: Your Personal, Serverless Proxy Network on Cloudflare GUIDE

Developer and cybersecurity specialist Luke (aka TurvSec) has introduced a powerful solution to this problem: FlareProx, an open-source tool that turns Cloudflare's global network into your personal HTTP proxy service.

Image

FlareProx leverages the power of Cloudflare Workers to deploy simple, effective HTTP proxy endpoints with a single command. It supports all HTTP methods, masks your IP address behind Cloudflare's massive infrastructure, and, best of all, runs on Cloudflare's generous free tier, giving you up to 100,000 free requests per day. This guide will take you on a deep dive into what FlareProx is, how it works, and how you can get it up and running in minutes.

How It Works: The Magic of Serverless Proxying

FlareProx isn't a traditional proxy server that you need to host and maintain. Instead, it operates on a serverless model using Cloudflare Workers—small, lightweight JavaScript functions that run on Cloudflare's edge network, close to the user. This architecture is what makes it so fast, scalable, and cost-effective.

When you make a request through a FlareProx endpoint, a simple yet powerful sequence of events unfolds:

  1. Request Routing: Your initial HTTP request is sent to one of your unique FlareProx Worker URLs (e.g., https://your-worker.account.workers.dev).
  2. URL Extraction: The Worker code instantly extracts the final destination URL. You can provide this target URL either as a query parameter (?url=...) or in a custom HTTP header (X-Target-URL).
  3. Request Proxying: The Worker then creates a new request and forwards it to your target URL, carrying over the method (GET, POST, etc.), headers, and body from your original request.
  4. Response Relay: The target server processes the request and sends its response back to the Cloudflare Worker.
  5. IP Masking & Final Response: The Worker relays this response back to you. Crucially, the target server never sees your real IP address; it only sees the IP address of the Cloudflare data center that processed the request. This provides an effective layer of privacy and IP rotation.

Quick Start: Deploying Your Proxies in 5 Steps

Step 1: Install Dependencies

First, clone the FlareProx repository from GitHub and install the required Python packages.

git clone https://github.com/MrTurvey/flareprox.git
cd flareprox
pip install -r requirements.txt

Step 2: Configure Cloudflare Access

FlareProx needs programmatic access to your Cloudflare account to manage Workers. You'll need an API Token and your Account ID.

  1. Sign in to your Cloudflare Dashboard.
  2. Navigate to My Profile > API Tokens.
  3. Click 'Create Token' and use the 'Edit Cloudflare Workers' template.
  4. Under 'Account Resources' and 'Zone Resources', ensure permissions are set to include your account.
  5. Create the token and copy it. Also, grab your Account ID from the main dashboard overview page.

Now, run the configuration command and paste in your credentials when prompted:

python3 flareprox.py config

This will save your details to a flareprox.json file.

Step 3: Deploy Proxy Endpoints

With configuration complete, you can create your proxy endpoints. The script automatically generates random names for each Worker to ensure they are unique.

# Create 2 proxy endpoints
python3 flareprox.py create --count 2

You can view your list of active proxy URLs at any time:

# View deployed endpoints
python3 flareprox.py list

Step 4: Use Your Proxies

Your proxies are now live. You can start sending requests through them immediately. FlareProx supports passing the target URL in two ways:

1. Query Parameter: Append ?url=https://target.com to your worker URL.
2. Custom Header: Send a request to the base worker URL with an X-Target-URL: https://target.com header.

# Method 1: GET request using a query parameter
curl https://your-worker.account.workers.dev?url=https://httpbin.org/ip

# Method 2: GET request using a custom header
curl -H X-Target-URL: https://httpbin.org/ip https://your-worker.account.workers.dev

# POST request with JSON data
curl -X POST -d '{key:value}' -H Content-Type: application/json \
  https://your-worker.account.workers.dev?url=https://httpbin.org/post

# DELETE request
curl -X DELETE https://your-worker.account.workers.dev?url=https://httpbin.org/delete

Step 5: Proxy Cleanup

When you're finished, you can easily remove all deployed Workers to keep your Cloudflare account tidy.

# Delete all proxy endpoints
python3 flareprox.py cleanup

Programmatic Usage: Integrating FlareProx into Your Applications

The true power of FlareProx is unlocked when you use it as a library within your own Python scripts for automation. This is ideal for web scraping tasks or automated testing pipelines. The repository includes an excellent example of how to do this.

#!/usr/bin/env python3
from flareprox import FlareProx, FlareProxError
import json

# Initialize FlareProx using your config file
flareprox = FlareProx(config_file=flareprox.json)

# Ensure it's configured
if not flareprox.is_configured:
    print(FlareProx not configured. Run: python3 flareprox.py config)
    exit(1)

# Create two endpoints if none exist
if not flareprox.sync_endpoints():
    print(Creating 2 new proxy endpoints...)
    flareprox.create_proxies(count=2)

# Prepare and send a POST request
try:
    post_data = json.dumps({username: testuser, message: Hello!})
    headers = {Content-Type: application/json}

    # The redirect_request method automatically picks a random endpoint
    response = flareprox.redirect_request(
        target_url=https://httpbin.org/post,
        method=POST,
        headers=headers,
        data=post_data
    )

    if response.status_code == 200:
        result = response.json()
        print(f✓ POST successful via FlareProx!)
        print(fOrigin IP Seen by Server: {result.get('origin', 'unknown')})
    else:
        print(fRequest failed with status: {response.status_code})

except FlareProxError as e:
    print(fFlareProx error: {e})

Core Use Cases: Who is FlareProx For?

  • Web Scraping: Effortlessly rotate your source IP by sending requests through different FlareProx endpoints. This helps avoid IP-based blocking and rate limiting from target websites.
  • Security Testing: Mask your true IP address during penetration tests to simulate an external attacker and avoid revealing your origin infrastructure.
  • API Development & Testing: Test how your API responds to requests from different geographical locations by leveraging Cloudflare's global network. Verify rate limiting and geo-specific features.
  • Load Testing: Distribute your test traffic across multiple, stable endpoints without having to manage a complex proxy infrastructure.
  • Privacy Enhancement: Add a simple, effective privacy layer between your personal machine and the servers you are communicating with.
FlareProx is designed for legitimate development, testing, and research purposes. Users are responsible for ensuring their usage complies with all applicable laws and terms of service. The authors assume no liability for misuse of this tool.
Important Disclaimer

Conclusion

FlareProx is a brilliant example of how modern serverless technology can solve old problems in a new, more efficient way. By standing on the shoulders of Cloudflare Workers, it provides a powerful, scalable, and virtually free proxy solution that is accessible to everyone. Whether you're a developer, a security researcher, or a data scientist, FlareProx is a valuable tool to add to your arsenal.

#flareprox