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 thewarp=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.
- After generating the
wgcf-account.toml
, use thelicense_key
from the file on your phone- Open the
1.1.1.1
app- Click on the hamburger menu button on the top-right corner
- Navigate to
Account
>Manage devices
and you’ll see your wgcf device there- Now, copy your WARP+ key back to
Account
>Key
and to thewgcf-account.toml
- After that, run this command
wgcf update
- After running the command, connect using WireGuard
- While connected, run this command to see if it works as expected
wgcf trace
- The result will show
warp=plus
instead ofwarp=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 3 years ago
- Reactions: 2
- Comments: 19
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 generatedwgcf-account.toml
file using vim thenwgcf update
step 4. Generate the profile withwgcf generate
, this should create thewgcf-profile.conf
step 5. Now connect using the generatedwgcf-profile.conf
I hope that works for you, it worked for me.
it works for me!!! thank you.
@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).
@martinsstuff Based on this Reddit post, it seems the
warp=on
problem can be reproduced by creating anew wgcf profile
. So, if we’re using theold generated wgcf profile
withwarp=plus
, there shouldn’t be any problem. But if we’re generating a new wgcf profile and then using awarp+ unlimited key
from the1.1.1.1
app, the wgcf doesn’t seem to switch towarp=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 .