WARP Configuration Generator

Русский | English

Open-source generator for Cloudflare WARP configs (WireGuard / AmneziaWG / Clash / Throne / Nekoray / Husi / Karing / WireSock). This is the public branch — no captcha, no analytics, no promo blocks. Deploy your own.

🚀 Quick Deployment

Docker (recommended)

Pre-built image is published to GHCR on every push to master:

docker run -d --name warp-generator \
  -p 3000:3000 \
  --restart unless-stopped \
  ghcr.io/nellimonix/warp-config-generator-vercel-public:latest

Open http://localhost:3000.

Docker — build locally

docker build -t warp-generator-public .
docker run -d -p 3000:3000 --name warp-generator warp-generator-public

docker-compose

services:
  warp-generator:
    image: ghcr.io/nellimonix/warp-config-generator-vercel-public:latest
    container_name: warp-generator
    ports:
      - "3000:3000"
    restart: unless-stopped

Vercel

• Or via CLI: vercel deploy
• Local dev: vercel dev

Netlify

• Or via CLI: netlify deploy
• Local dev: netlify dev

Cloudflare Workers

• Or via Wrangler: wrangler deploy
• Local dev: wrangler dev

Cloudflare Pages

The same wrangler.jsonc deploys to Pages with the static export.

CLOUDFLARE_WORKERS=1 npm run build
npx wrangler pages deploy out --project-name=warp-generator

Or connect the repo in the Cloudflare dashboard:

• Build command: CLOUDFLARE_WORKERS=1 npm run build
• Output directory: out

🛠️ Local Development

npm install
npm run dev          # dev server on :3000
npm run build        # production build
npm run start        # serve production build
npm run lint

⚙️ Generator Options and API

The generator exposes the same options in the UI and in POST /api/generate:

Option	Behavior and constraints
DNS	Providers come from config/dns.ts. Community providers are marked with •; selecting one forces All sites and clears selected services because they do not support split tunneling. An unknown provider ID falls back to Cloudflare DNS.
IPv6	Enabled by default. Disabling it removes IPv6 from the interface address, DNS list, and the default all-sites AllowedIPs.
Exclude LAN	Available only in All sites mode. It replaces the default routes with public address ranges so private/reserved LAN ranges stay outside the tunnel.
PersistentKeepalive	Disabled by default. Enabling it with an empty UI field uses 25; the API accepts integers from 1 through 65535 and omits invalid values. It is emitted by WireGuard and WireSock configs.
Custom I1	A non-empty value is trimmed and must be at most 253 characters with no whitespace. AmneziaWG WireGuard uses it to generate a QUIC I1 mask; WireSock uses it as Id. Empty or invalid input silently falls back to a bundled random mask/domain.

Example request against a local deployment:

curl -X POST http://localhost:3000/api/generate \
  -H 'Content-Type: application/json' \
  -d '{
    "selectedServices": [],
    "siteMode": "all",
    "deviceType": "awg15",
    "endpoint": "engage.cloudflareclient.com:4500",
    "configFormat": "wireguard",
    "dnsId": "cf",
    "ipv6": false,
    "excludeLan": true,
    "persistentKeepalive": 25,
    "customI1Domain": "google.com"
  }'

A successful response has success: true and a content object containing configBase64, qrCodeBase64, configFormat, and fileName. configBase64 contains the Base64-encoded configuration; qrCodeBase64 is an image data URL.

➕ Adding a new service (PR welcome)

The "specific sites" mode lets users select services to route through WARP. To add one:

1. Fork the repo and create a branch (e.g. feat/service-newsite).
2. Create config/services/<your-service-key>.json:

   {
     "name": "Display Name",
     "icon": "FaIconName",
     "iconLibrary": "fa",
     "type": "new",
     "ips": "1.2.3.0/24, 5.6.7.0/24, ..."
   }

   • name — user-visible service name.
   • icon — icon name from react-icons. Verify the name exists in the chosen library.
   • iconLibrary — one of: fa, fa6, si, bi, md, ri, etc. (matches react-icons sub-package).
   • type — optional. Set "new" to show a "NEW" badge.
   • ips — comma-separated CIDR ranges. Use a real ASN/IP lookup tool — Cloudflare's whois, BGP.tools, or whois -h whois.cymru.com " -v <ip>".
3. Do NOT edit worker/api-handler.js or functions/api/generate.js. A GitHub Action (build-ip-ranges) rebuilds the IP_RANGES blocks in both files automatically on merge to master, and syncs the new service into the production branch.
4. Open a PR to master.

Local preview of the rebuild

node scripts/build-ip-ranges.mjs

Runs against config/services/*.json and rewrites the // IP_RANGES:BEGIN ... // IP_RANGES:END block in both worker/functions files. Safe to run repeatedly — idempotent.

Adding a DNS provider

1. Add the provider to DNS_PROVIDERS in config/dns.ts with a unique id, display label, IPv4/IPv6 arrays, and isCommunity.
2. Set isCommunity: true if the provider cannot be used with specific-site routing. Both the UI and API enforce the all-sites restriction.
3. Mirror the entry in the embedded DNS_PROVIDERS arrays in worker/api-handler.js and functions/api/generate.js. Unlike IP ranges and I1 masks, DNS providers do not currently have an automatic sync script.
4. Run npm run build before opening the PR.

Docker and Vercel use config/dns.ts directly, while Cloudflare Workers and Netlify execute the embedded handlers. Keeping all three provider lists in sync prevents a provider shown by the static UI from falling back to Cloudflare DNS at generation time.

Maintaining default I1 masks

lib/builders/shared.ts is the source of truth for masks used when no custom I1 domain is supplied:

1. Edit only the I1_MASKS array between the // I1_MASKS:BEGIN and // I1_MASKS:END markers.
2. Run node scripts/build-i1-masks.mjs.
3. Commit the generated changes to worker/api-handler.js and functions/api/generate.js with the source change.

The script validates the markers and mask format, updates both embedded handlers, and is idempotent. The build-i1-masks workflow also runs when its source, script, or workflow changes on master and rebuilds the production handlers. Do not hand-edit generated I1 blocks.

📁 Project Structure

├── app/
│   ├── layout.tsx                 Root layout (Geist font, meta)
│   ├── page.tsx                   Server component — loads services
│   ├── not-found.tsx              404 page
│   └── api/generate/route.ts      POST endpoint (config generation)
│
├── components/
│   ├── home-client.tsx            Client shell (tabs, state)
│   ├── layout/
│   │   ├── topbar.tsx             Logo + tab navigation
│   │   ├── sidebar.tsx            GitHub link + server list (sticky)
│   │   └── footer.tsx
│   ├── generator/
│   │   ├── config-selectors.tsx   Custom dropdowns (format, device, etc.)
│   │   ├── advanced-settings.tsx  IPv6, keepalive, and custom I1 controls
│   │   ├── service-picker.tsx     Service selection grid
│   │   ├── result-panel.tsx       Download / copy / QR result block
│   │   ├── formats-tab.tsx        Supported formats list
│   │   └── about-tab.tsx          About + compatible clients
│   └── icons/                     Icon resolver + flag icons
│
├── config/
│   ├── services/                  JSON files — one per service (IP ranges)
│   ├── services-loader.ts         Auto-loads all JSONs at startup
│   ├── dns.ts                     DNS providers and split-tunnel constraints
│   ├── endpoints.ts               Cloudflare WARP endpoints
│   └── formats.ts                 Config format definitions
│
├── lib/
│   ├── builders/                  One file per config format
│   │   ├── wireguard.ts
│   │   ├── throne.ts
│   │   ├── clash.ts
│   │   ├── nekoray.ts
│   │   ├── husi.ts
│   │   ├── karing.ts
│   │   ├── wiresock.ts
│   │   ├── shared.ts              Device profiles and default I1 masks
│   │   └── index.ts               Dispatcher — buildConfig(format, params)
│   ├── warp-service.ts            Orchestrator (keys → CF → build → QR)
│   ├── quic.ts                    Custom QUIC I1 mask generation
│   ├── cloudflare-client.ts       Cloudflare WARP API registration
│   ├── crypto.ts                  Key generation (tweetnacl)
│   ├── qr-generator.ts            QR via external API + SVG fallback
│   └── ip-ranges.ts               Re-exports from services-loader
│
├── hooks/
│   ├── use-generator.ts           Client-side generation logic
│   └── use-mobile.ts              Responsive breakpoint hook
│
├── scripts/
│   ├── build-ip-ranges.mjs        Regenerates IP_RANGES in worker + functions
│   └── build-i1-masks.mjs         Regenerates I1_MASKS in worker + functions
│
├── worker/                        Cloudflare Workers runtime
├── functions/                     Netlify Functions runtime
├── types/                         TypeScript type definitions
├── styles/globals.css             Design tokens + dark theme
├── .github/workflows/             CI: Docker, IP_RANGES, I1_MASKS rebuilds
├── Dockerfile                     Standalone production build (public)
├── next.config.mjs
└── package.json

🔧 Configuration

No environment variables required for the public build. The generator runs anonymously against the public Cloudflare WARP registration API.

Build modes

next.config.mjs switches output based on environment:

Env var	Output	Used by
DOCKER_BUILD=1	standalone	Docker / Dokploy
CLOUDFLARE_WORKERS / CF_PAGES	export	CF Workers / CF Pages
none	default	Vercel / Netlify

🌐 Supported Platforms

Platform	Support	Notes
Docker (self-host)	✅ Full	standalone Next.js server
Vercel	✅ Full	default runtime
Netlify	✅ Full	Edge functions
Cloudflare Workers	✅ Full	static export + worker
Cloudflare Pages	✅ Full	static export

📄 License

MIT License — see LICENCE

🤝 Contributing

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Open a Pull Request

🔗 Mirrors / Alternative Links

• Telegram Bot: t.me/warp_generator_bot
• Main Site: warp3.llimonix.pw
• Vercel Mirror: warply2.vercel.app
• Netlify Mirror: getwarp2.netlify.app
• Cloudflare Mirror: warp.llimonix.workers.dev
• Telegram Channel: ллимоникс </>