mrkeyoor.comAsk

ViRb3/wgcftested 09 Oct 2026commit ace873c

wgcf review

Use wgcf when you need a portable WARP profile and can operate the separate WireGuard client and its routes.

  • README install 61 s
  • README usage failed
8/8tests passed
  • Install 140 s
  • Build 27 s
Dev Toolsevaluationupdated 17 Nov 2026
+12stars / 7d

wgcf is an unofficial, cross-platform CLI for Cloudflare WARP. It registers accounts and generates profiles for separate WireGuard software. Users describe moving those profiles between computers, routers and televisions.

Verdict

Use wgcf when you need a portable WARP profile and can operate the separate WireGuard client and its routes. Skip it when you require an official Cloudflare application, delivered native Teams enrollment or a dependable streaming improvement. Our November registration task exited 1; October's repository commands succeeded.

wgcf infographic: generate WARP profiles for separate WireGuard software, plus our test result and who it suits
Tested 16 November 2026: the README command failed with "Error types: (1)". Before that: 9 Oct: 8 of 8 source tests passed; go install took 61 s.

We ran it

Lab card: what happened when we ran wgcf
Lab card from our sandbox run
Screenshot of wgcf (github.com/ViRb3/wgcf)
github.com/ViRb3/wgcf
Install✓ · 140s66 packages
Build✓ · 27s
Tests✓ · 8s8 passed · 0 failed of 8 (go test)
Repo135 files~18,210 lines of source · 0.8 MB · 2 CI workflows · Dockerfile

Answers from our run

Does wgcf build from source?

Dependencies installed in 140 seconds (66 packages), and the build succeeded in 27 seconds. We cloned commit ace873c into a clean Debian container with 3 CPUs and no project-specific setup.

Do wgcf's tests pass?

Yes. The project's own test command finished in 8 seconds and reported 8 passed, 0 failed (go test).

Who should not use wgcf?

Anyone requiring an official Cloudflare application.

What are the alternatives to wgcf?

Official Cloudflare WARP client, wireguard-tools. Use wgcf when you need a portable WARP profile and can operate the separate WireGuard client and its routes.

Setup3/5In our 2026-11-16 run it installed in 61 s, but the README’s “Register new account” command failed as written with “Error types: (1) *withstack.withStack (2) *withstack.withStack (3) *e…”.Editor’s note: October repository commands succeeded, but November registration exited 1. The supplied results do not support a numerical judgment for completed tunnel setup.
Docs3/5The README has an install section (“Download”) and a usage section (“Usage”), but its “Register new account” command failed as written in our 2026-11-16 run (“Error types: (1) *withstack.withStack (2) *withstack.withStack (3) *e…”).Editor’s note: The README documents commands, filenames and WARP+ binding, but the evidence does not assess documentation across the intended device workflows.
Community4/5Last push on 2026-11-16, 8,904 stars and maintainers answered or closed 10 of the 10 most-discussed issues we sampled.Editor’s note: Sampled issues show investigation and individual remedies, without measurements of response times, support capacity or failure frequency.
Maturity5/5Latest release v2.3.1 on 2026-10-11, repository created 2020-04-13 and its test suite passed in our sandbox (8 of 8 passed).Editor’s note: Passing repository commands and compatibility maintenance do not supply completed-tunnel or long-running reliability evidence for a numerical judgment.

How we score

Who it’s for

Operators who need a portable WARP profile for a separate WireGuard client.
Router users who can manage tunnel routes and retain a recovery route.
Windows users preparing profiles for Android TV or Firestick through the attributed community workflows.

Who it’s NOT for

Anyone requiring an official Cloudflare application.
Teams requiring delivered native Teams or Zero Trust enrollment in wgcf.
WARP+ users relying on referral keys, which upstream excludes.
Viewers choosing software on the expectation of a dependable buffering improvement.

Setup reality

Our October 9, 2026 sandbox at ace873c recorded a successful 140-second install with 66 dependencies, a successful 27-second build and a successful 8-second test step. The stored test summary is 8 passed, 0 failed of 8. The configured sandbox had 3 CPUs, 8 GB RAM and image golang:1.24-bookworm.

The November 16 run recorded checkout de6bba7147dc and installed wgcf through Go using @latest. Installation recorded 20.1 MB in 61.1 seconds. Help succeeded; the unsupported --version probe and registration each exited 1. Registration stack paths reference v2.3.1. November used an unprivileged container labeled golang:1.24-bookworm with 2 CPUs, 4 GB RAM, no published ports and no secrets.

The README separates registration, profile generation and connection through WireGuard software. WARP+ instructions require immediate purchased-key binding on a fresh account before other commands or a connection. The body’s testing-limit section explains executable identity, runtime evidence and test-count reconciliation.

Short answer: use it when you need a portable WARP profile

Use wgcf when you need a WARP profile for separate WireGuard software and can manage that client's routing. Our November 16 registration attempt exited 1, while wgcf's help command succeeded. Choose an official application if that is your requirement, and skip wgcf as a purchase justified by promised streaming improvements. The practical decision is whether a portable profile solves your device problem. Our registration result and the README workflow describe different stages of that job.

wgcf is an unofficial, cross-platform CLI for Cloudflare WARP. Its README lists account registration, subscription-key changes, WireGuard profile generation, account status and connection tracing. A computer can prepare a configuration for another device, as the television reports below illustrate. That makes wgcf useful when the destination runs WireGuard software and the preparation machine runs the CLI. The generated file is the handoff between those two programs; the WireGuard client operates the tunnel.

What people use wgcf for

Users describe wgcf profiles on Gentoo, OpenWrt, Android TV and Firestick, with outcomes tied to their own connections. The Maui gaming account concerns endpoint selection, the OpenWrt account concerns IPv6 access, and the television accounts concern preparing a configuration elsewhere. These are concrete reasons to consider the tool. Their reports also help identify which part of a setup needs attention: profile creation, transfer, tunnel routing or application behavior.

Who used it What they did Reported outcome
The Tech Nexus author in Maui Prepared a Gentoo profile for Japanese FFXIV servers Reported 177 ms without a VPN and 160 ms through the initial desktop tunnel; switching the resolved endpoint from IPv6 to IPv4 changed the selected location from Los Angeles to Honolulu. Gaming report
Dariusz Więckiewicz Added WARP to OpenWrt for IPv6 Reported avoiding the severe limitation of his previous 6in4 tunnel, which ran at 10% of his full connection speed. OpenWrt report
sas46 on r/AndroidTV Prepared a Windows 11 profile for a Xiaomi MiBox Reported restored access after provider DNS blocking affected an IPTV service. Android TV workflow
LivingNecessary9789 on r/firestick Prepared a Windows profile and transferred it with the WireGuard Android client Described this route after router DNS changes proved insufficient and a sideloaded official APK failed to work properly. Firestick workflow

The Android TV workflow separates preparation from connection: generate wgcf-profile.conf on the computer, transfer the file, install the WireGuard Android client and import the configuration on the television. The Firestick author used Windows and ADB for a similar handoff. Playback reports differ: levider reported help with TorBox in Nuvio/Stremio, dv83d reported slower playback with more buffering, and Firestick commenter TechFuz reported slightly worse playback after connecting. TorBox discussion and Firestick follow-up preserve those differing outcomes.

What happened when we ran it

November installation and help succeeded, but registration exited 1; October repository commands succeeded. Our November 16, 2026 run recorded checkout de6bba7147dc and installed wgcf through Go using @latest. Registration stack paths reference v2.3.1. The configured environment was an unprivileged golang:1.24-bookworm container with 2 CPUs, 4 GB RAM, no published ports and no secrets. The assigned task was the README's account-registration command.

Hands-on question Answer Verdict Why
Was a checkout recorded? The clone step recorded recipe quickstart-cli in 1 second. Recorded The run identifies checkout de6bba7147dc.
How was wgcf installed? Go installation recorded 20.1 MB in 61.1 seconds. Installed The command was go install github.com/ViRb3/wgcf/v2/...@latest.
Did wgcf --version work? Exit 1 after 0.1 seconds, with Error: unknown flag: --version. Failed probe Usage text accompanied the error.
Did wgcf --help work? Exit 0 after 0.1 seconds, with command help. Passed The executable launched and printed its command list.
Did wgcf register complete? Exit 1 after 0.1 seconds. Failed The usage finding lists stack-wrapped error types.
Was cleanup recorded? Teardown: OK. Completed The teardown record reports success.

The version finding matters because usage output can resemble successful help when read without the exit code. Here, the unsupported flag failed, and the subsequent help command succeeded. Registration was a separate failure: its finding lists *withstack.withStack twice and *errors.errorString. Those names describe the recorded error wrappers. The run therefore contains both a successful executable launch and an unsuccessful account task. Version finding and registration finding keep those outcomes distinct.

Our October 9, 2026 repository run at ace873c recorded successful install, build and test steps. Installation took 140 seconds and recorded 66 dependencies; build took 27 seconds; tests took 8 seconds. October describes repository-command outcomes, while November describes an attempted account-registration workflow. These are different tasks, so their results answer different questions. The October measurements come from our sandbox harness, rather than a README test count.

October repository step Outcome Duration
Install Succeeded; 66 dependencies recorded 140 seconds
Build Succeeded 27 seconds
Tests Succeeded; stored summary: 8 passed, 0 failed of 8 8 seconds

October's configuration listed 3 CPUs, 8 GB RAM and golang:1.24-bookworm. The checkout contained 135 files, approximately 18,210 source lines and occupied 0.8 MB. Repository signals included two CI workflow files and a Dockerfile, with no tests directory. Tests can sit beside Go source files, so the directory observation and successful test command describe compatible facts. The earlier MrKeyoor account also records repeated successful package lines in its supplied log tail.

Where people get stuck: account errors and tunnel errors

Issue #50 and issue #158 separate device-specific tunnel failures from failures across devices while the official client works. The maintainer directs the first pattern toward system configuration and attributes the second to possible regional abuse-prevention restrictions. This gives readers a useful first comparison: try the same profile on another device and record whether the official client connects. The system issue and cross-device issue remain open in the supplied evidence.

Symptom Attributed finding Response recorded in the evidence
Purchased-key linking returns 400 Bad Request pverghese in #68 had reached five linked devices Removing a device allowed linking to succeed. Issue #68
Registration returns HTTP 429 on 2.2.31 Reporters compared failures with 2.2.30 The maintainer supplied builds restoring the older TLS fingerprint; Windows and macOS testers reported success. Issue #613
A profile fails on Ubuntu but works elsewhere matroot reported loading the WireGuard module That user reported success; other contributors discussed MTU changes. Issue #50
Unofficial tunnels fail across devices while official WARP works The maintainer identifies regional restrictions as a likely explanation The maintainer recommends the official client. Issue #158
Gluetun rejects file-based endpoint handling peterweissbier supplied the endpoint IP through an environment variable The reporter said the container accepted it. Issue #279

The 429 discussion records an investigation into a version-dependent TLS fingerprint, whereas #68 separately describes apparent IP rate limiting after extensive API testing, including trouble in the official phone app. Endpoint advice also changes over time: a January 2025 update in #279 says previously suggested addresses in 162.159.193.0/24 stopped working for reporting users and qualifies availability by region. These threads concern different symptoms and histories. API-limit account, endpoint update.

WARP+ binding comes before the first connection

The README tells affected WARP+ users to register a fresh account and immediately bind the purchased subscription key before other commands or a tunnel connection. It supports subscriptions purchased directly through the official 1.1.1.1 app and excludes referral keys. The documented sequence continues with wgcf update --license-key "YOUR_LICENSE_KEY_GOES_HERE" and wgcf generate. It also states a maximum of five linked devices and directs users to remove devices through the phone app. Upstream subscription instructions.

Issue #85 contains successful reports alongside continuing complaints. WinkelCode described importing a generated profile into Windows WireGuard and immediately seeing warp=plus. The maintainer's August 23, 2025 note says an account that previously connected can remain at warp=on after correct-key binding. After connecting the generated profile, the README instructs readers to run wgcf trace and look for warp=on or warp=plus. Those are the documented status labels. WARP+ discussion records the account-history distinction.

Router routing changes can remove access to services

Dariusz Więckiewicz reported that default routing through WARP made his existing WireGuard server and Cloudflare Zero Trust tunnel inaccessible from the internet. He removed 0.0.0.0/0 from the peer routing configuration to retain ordinary IPv4 routing while using WARP for IPv6. The same guide describes a temporary loss of internet connectivity when applying route changes. For a router deployment, record which traffic should enter WARP and retain a way to reach the router while changing routes. OpenWrt routing account.

Other reports show why the destination setup matters. In #50, felipejfc said WARP worked on a Linux host but downstream LAN devices using it as a gateway achieved lower download speeds. The Puppy Linux guide describes removing AllowedIPs = ::/0 for FatDog902 after its IPv6 routing configuration prevented startup; its later FatDog903 instructions describe kernel configuration improvements. These are distinct gateway and operating-system reports, each attached to its original setup. Gateway report, FatDog guide.

Security: the generated profile contains a private key

The FatDog example places PrivateKey under [Interface], beside addresses and DNS settings. Handle the generated profile as a credential when transferring it to a router or television: redact key material from diagnostics and keep account files out of public repositories. These are handling recommendations based on the file contents. The CLI workflow requires moving a usable configuration between devices, so the transfer itself deserves the same care as the machine that created it. Profile example.

The upstream README expressly disclaims affiliation with Cloudflare and documents local terminal commands. Registration uses Cloudflare's service, while the profile is generated for separate WireGuard software. Create the files on a machine you control and enter subscription material locally as the documented commands require. This recommendation follows the supplied workflow and credential format; it does not depend on choosing a hosted generator. Project disclaimer and command reference identify the software and its relationship to Cloudflare.

wgcf vs the official WARP client and wireguard-tools

wgcf generates WARP profiles, while wireguard-tools configures WireGuard tunnels. The official WARP application is the maintainer's recommendation for the cross-device failure pattern in #158. Choose according to the job you need completed: account and profile preparation, an official application, or operation of an existing WireGuard configuration. That distinction also explains why wgcf and wireguard-tools can belong in the same setup rather than competing for the same role.

Choice Evidence-supported role Pick it when
wgcf Account registration and profile generation You need a portable WARP profile. README
Official Cloudflare WARP client Official application recommended in #158 Unofficial tunnels fail across devices while it works. Maintainer recommendation
wireguard-tools Userspace tools including wg and wg-quick You need to configure a WireGuard tunnel. WireGuard tools README
A 6in4 IPv6 tunnel Więckiewicz's previous IPv6 approach Compare its behavior with WARP on the connection where you will use it. Author's comparison

The Firestick author's comparison began with router DNS set to 1.1.1.1, continued through a sideloaded official APK, and ended with a wgcf profile imported into WireGuard. Their reason for changing tools was a device workflow that had failed to solve stream lag. The later comment reporting worse playback belongs beside that account. Together, those reports make the transfer workflow useful to understand without turning one person's outcome into a speed ranking. Firestick comparison.

What the other reviews get wrong

The upstream output filenames are wgcf-account.toml for the account and wgcf-profile.conf for the WireGuard profile. The OpenWrt guide instead names wgcf-profile.toml, while the FatDog guide names wgcf-account.conf. Follow upstream's default names, or explicitly account for a renamed file before importing it. The discrepancy matters because the account file and the tunnel configuration serve different purposes. Upstream filenames, OpenWrt guide, FatDog guide.

The README describes MTU 1280 as a compatibility default and says increasing it may improve speed. The OpenWrt guide calls it a recommended maximum, which changes the meaning of the advice. The archived fork's subscription instructions also omit the current fresh-account warning. Use the current upstream binding sequence when following that older material. These corrections concern the supplied instructions themselves: the default MTU, account history and command order. Current README, archived instructions.

The Scoop listing calls 2.2.15 current, while FreshPorts records an update to 2.3.1 on November 9, 2026. Upstream metadata supplied for this review identifies release v2.3.1 dated October 11, 2026. Those are different records: a listing label, a packaging update and an upstream release. For upstream binaries, the README directs users to the project's releases page. Scoop listing, FreshPorts history, upstream releases.

Argusic's successful attempt reports account registration and profile generation, with trace output warp=off. Its history also lists a later unsuccessful attempt, despite text presenting two measurements as evidence against a one-off result. An X post lists wgcf as having run in that evaluation. Our earlier page needs a narrower test-count description too: eight is the stored parser summary, and that page describes repeated successful package lines. Argusic record, X listing, earlier MrKeyoor page.

FAQ

wgcf registers WARP accounts and generates profiles for separate WireGuard software. Its README's basic sequence is registration followed by profile generation, with purchased WARP+ keys requiring the immediate binding sequence described above. A computer can prepare a profile for another device: the Windows and television reports below describe that handoff, while the issue discussions distinguish account errors from failures after a WireGuard client connects. Upstream command reference.

What is wgcf, and how do I use it with Cloudflare WARP?

The README's basic sequence is wgcf register followed by wgcf generate. Registration saves wgcf-account.toml; generation saves wgcf-profile.conf. Import the profile into WireGuard software, connect it, and then run wgcf trace for the documented WARP status check. Readers binding a purchased WARP+ subscription should follow the immediate binding sequence before generation and connection. This is the upstream workflow, with separate commands for creating account data and producing the client configuration. README instructions.

Where can I find the wgcf GitHub repository and download the correct binary?

The repository is ViRb3/wgcf, and its README links to precompiled binaries on the releases page. Choose a binary for the operating system and CPU of the machine running the CLI. The OpenWrt author illustrates this by selecting an ARMv7 executable for that router. A profile prepared on Windows can instead be transferred to a television running a WireGuard client, as the Android TV report describes. GitHub repository, release downloads, architecture example.

How do I generate a WARP configuration on Windows?

sas46's Windows 11 workflow downloads the Windows executable, renames it wgcf.exe and opens a terminal in its folder. The current README supplies the registration and generation commands, plus the purchased-key binding sequence for WARP+. WinkelCode's issue #85 report shows Windows PowerShell invocation with a local executable path and describes importing the generated file into the WireGuard client. Use the binary's actual filename when applying that command form. Windows workflow, Windows issue report.

Can wgcf be used online, or does it need to run locally?

The supplied README documents a local terminal program and downloadable executables. Registration contacts Cloudflare's service; generation produces a file for WireGuard software. The Firestick and Android TV reports use a computer to prepare that file and another device to connect it. This separates the machine running wgcf from the machine using the resulting tunnel, which is the practical distinction for those device workflows. README, Android TV account, Firestick account.

Does wgcf support Cloudflare Teams or Zero Trust?

Issue #56 remains an open Teams/Zero Trust support request in the supplied record. The maintainer said support was not expected in the foreseeable future and welcomed pull requests. The discussion includes requests for native WireGuard use and offers to help. Loopback 27's official-client setup video instead shows dashboard organization steps, including choosing a team name and device-enrollment permissions. These describe different enrollment workflows. Teams request, official-client walkthrough.

Why does my paid WARP+ account show warp=on instead of warp=plus?

The README attributes this failure case to an account that connected before the purchased key was bound and instructs affected users to start with a fresh account. Issue #85 records successful fresh-account reports and continuing complaints. Issue #459 was closed as a duplicate of #85. Follow the current upstream command order rather than an older guide that only says to replace a key and regenerate the profile. README warning, WARP+ reports, duplicate issue.

Why does internet access stop after bringing up the generated WireGuard profile?

The maintainer separates system-specific failures in #50 from the cross-device pattern in #158. One Ubuntu user reported success after loading the WireGuard module; others described MTU changes and different network conditions. The maintainer recommends the official client for the pattern where unofficial tunnels fail across devices while it works. Compare the same profile on another device before choosing a remedy from a comment. System-specific reports, cross-device reports.

Why does wgcf registration return HTTP 429, and can the version affect it?

Issue #613 records comparisons between 2.2.30 and 2.2.31, followed by successful reports for maintainer-supplied builds restoring the older TLS fingerprint. Issue #68 separately describes apparent IP rate limiting after extensive API testing. Save the executable version, command and actual error when comparing your case with those threads. Their different histories explain why a shared HTTP status alone is insufficient to select the same response. Version-dependent report, API-limit report.

What we have not tested yet

Neither our October repository checks nor November's registration attempt demonstrated an active WARP tunnel. Our runs provide no gaming-latency, streaming-throughput, IPv6, DNS, WARP+ routing, router-operation or Windows-to-TV transfer measurements. The community accounts are attributed observations. The supplied pack also contains no security audit or long-running reliability result. The Maui account has no final ping measurement after its endpoint change, and the playback reports provide no controlled explanation for their conflicting outcomes.

November's binary-to-checkout relationship is unverified: the checkout is de6bba7147dc, installation uses @latest, and registration stack paths reference v2.3.1. The underlying registration error is absent, so its cause cannot be assigned to Cloudflare rejection, terminal interaction or container networking. Image labels describe configured images rather than the compiler or operating-system version that completed a command. The earlier page records a Go 1.26.0 download, while November's truncated stack contains a Go 1.26.11 toolchain path; neither substitutes for complete runtime logs.

October's eight passes remain a parser summary rather than a reconciled count of unique tests. The earlier page describes repeated successful package lines, and complete logs are absent. Argusic's later unsuccessful attempt also lacks an explanation in the supplied material. Its successful registration and generation record, with warp=off, establishes that attempt's reported outcomes rather than an active tunnel or two successful replications. These distinctions preserve the recorded command successes without extending them to a completed connection.

The supplied discussions leave the practical meaning of paid-account warp=on unresolved: cosmetic-status and routing explanations conflict, and controlled route or throughput measurements are absent. The eventual release containing #613's supplied-build fix is unspecified, as is a recovery interval for #68's apparent rate limit. Historical endpoint comments provide no current universal replacement list, and the Gluetun report lacks a complete worked configuration. FreshPorts' update and the stale Scoop label also say nothing about what a current Scoop installation downloads.

No-Fee7369's question about simultaneous profiles sharing interface IPs, endpoints and public keys lacks a substantiated technical answer. The VPS SMTP request lacks a confirmed port-specific bypass, and the #619 handshake-but-HTTPS-timeout account appears only through our earlier page, which leaves the keepalive suggestion unresolved. The gateway report likewise ends without a solution for downstream speed. A useful next run would complete registration, import the profile and send application traffic on a named network while recording the exact binary and routes. Profile question, SMTP request, earlier account.

Alternatives

ProjectWhat it isPick it when
Official Cloudflare WARP clientCloudflare's official WARP application.Choose it when you require the official application, particularly for the issue #158 pattern where unofficial tunnels fail across devices while the official client works.
wireguard-toolsUserspace tools for configuring WireGuard tunnels, including wg and wg-quick.Use it to operate an existing WireGuard configuration, including a generated profile. It complements wgcf's account-registration and profile-generation role.

Sources

  1. wgcf upstream README
  2. System-specific connectivity reports
  3. Cross-device connectivity reports
  4. WARP+ account-binding discussion
  5. Android TV community workflow
  6. WireGuard tunnel utilities

More dev tools reviews