wgcf: WARP+ not work

According to @galpt in #84 and this Reddit discussion, some people are having problems with WARP+ after changing their key. If you are one of these people, please post here so I can track the significance of this issue. I will try to investigate in the next few days, but until then, @galpt has posted a workaround:

How to fix the WARP+ issue

Based on this post, some people are unable to get the warp=plus working and only get the warp=on even after they’ve changed the license key. However, you can solve this issue with some simple steps:

⚠️ Please save the WARP+ key on your phone before doing any of these steps.

  1. After generating the wgcf-account.toml, use the license_key from the file on your phone
  2. Open the 1.1.1.1 app
  3. Click on the hamburger menu button on the top-right corner
  4. Navigate to Account > Manage devices and you’ll see your wgcf device there
  5. Now, copy your WARP+ key back to Account > Key and to the wgcf-account.toml
  6. After that, run this command
wgcf update
  1. After running the command, connect using WireGuard
  2. While connected, run this command to see if it works as expected
wgcf trace
  1. The result will show warp=plus instead of warp=on

[Note] If it doesn’t work, you probably have to repeat step 1-5 since the fix is between these steps.

About this issue

  • Original URL
  • State: open
  • Created 6 years ago
  • Reactions: 2
  • Comments: 27

Most upvoted comments

I had the same issue but now I got it to work, thanks to adldeez.

step 1. Delete the wgcf-account.toml and also the generated profile step 2. Register new account with wgch register step 3. Add the license key to your generated wgcf-account.toml file using vim then wgcf update step 4. Generate the profile with wgcf generate, this should create the wgcf-profile.conf step 5. Now connect using the generated wgcf-profile.conf

I hope that works for you, it worked for me.

Had to comment because just recently I noticed my wireguard profiles previously generated with wgcf weren’t using WARP+ (yes, I have WARP+ subscription officially through the 1.1.1.1 app and these previously generated profiles were using WARP+ license and working correctly). I can connect with the 1.1.1.1 app and it says warp=plus. I tried to generate new profile with new account key from 1.1.1.1 app, but it still says warp=on even though the Account type says unlimited from wgcf status and I can see the profile registered in the 1.1.1.1 app. Happy to provide more information if needed.

Edit 1: 1.1.1.1 app is now default to MASQUE protocol, when switching to Wireguard, it has the same problem. Might be cloudflare’s side problem.

@galpt When I set it up on the new PC (a couple days ago) I ran these commands:

.\wgcf_2.2.3_windows_amd64.exe register

(then I inserted the license key into the profile)

.\wgcf_2.2.3_windows_amd64.exe update

.\wgcf_2.2.3_windows_amd64.exe generate

I then loaded the generated profile into the WireGuard client and it immediately worked with Warp+ (warp=plus).

Did some clicking around

  • 1.1.1.1 app with WARP+, but switched in settings to Wireguard: warp=on
  • 1.1.1.1 app with WARP+, but left on Auto or MASQUE: warp=plus

So yes, from the looks of it, even the official 1.1.1.1 app with WARP+ will be warp=on when using Wireguard instead of MASQUE. Bummer

I had the same issue but now I got it to work, thanks to adldeez. step 1. Delete the wgcf-account.toml and also the generated profile step 2. Register new account with wgch register step 3. Add the license key to your generated wgcf-account.toml file using vim then wgcf update step 4. Generate the profile with wgcf generate, this should create the wgcf-profile.conf step 5. Now connect using the generated wgcf-profile.conf I hope that works for you, it worked for me.

These exact steps worked for me. Thank you.

this works the sequence is very important, if you run wgcf update/generate first, then update the license key and run wgcf update/generate again, the connection still remains as a free plan

I think it might be because this PR https://github.com/ViRb3/wgcf/pull/355 to fix the IPv6 connectivity the ipv6 address is bonded to the private key at the first update/generate

so we have to update the license key with the PLUS key the very first time when the bond is done, update without changing the private key won’t change your plan to PLUS I think this is a Cloudflare issue because the official client also has this problem https://community.cloudflare.com/t/losing-ipv6-connectivity-with-warp/568971

this behavior should be documented for now until the issue is resolved by Cloudflare

I had the same issue but now I got it to work, thanks to adldeez.

step 1. Delete the wgcf-account.toml and also the generated profile step 2. Register new account with wgch register step 3. Add the license key to your generated wgcf-account.toml file using vim then wgcf update step 4. Generate the profile with wgcf generate, this should create the wgcf-profile.conf step 5. Now connect using the generated wgcf-profile.conf

I hope that works for you, it worked for me.

it works for me!!! thank you.

@martinsstuff Based on this Reddit post, it seems the warp=on problem can be reproduced by creating a new wgcf profile. So, if we’re using the old generated wgcf profile with warp=plus, there shouldn’t be any problem. But if we’re generating a new wgcf profile and then using a warp+ unlimited key from the 1.1.1.1 app, the wgcf doesn’t seem to switch to warp=plus.

Not sure if “after changing their key” refers to someone with a new license/subscription (I have had mine for a while now) but I have been using WGCF since the python version and set it up just recently on a new PC and everything (Warp+ included) works fine, didn’t have to do anything special, just worked by following the normal instructions.

I remember when I first set it up using the python version, I did have issues where it would show up as Warp free but it just fixed itself after a bit.

Edit: I regularly check the trace website whenever I use WARP+ so it’s not intermittent, it works consistently showing up as “warp=plus”.

Former

TCP/IP Fingerprint

OS | Linux 2.2-3.0 Link | Ethernet MTU | 1500 Distance | 5 Hops

Now TCP/IP Fingerprint OS Windows (NT kernel) Link generic tunnel or VPN MTU 1420 Distance 13 Hops

Warp+ never uses argo tunnel now. so, now, Warp+ = Warp free .