No more warp=plus about wgcf HOT 39 CLOSED

I have sent an e-mail to Cloudflare and am now waiting for a response. Will keep you updated here.

from wgcf.

@beygolu Please create a new issue for unrelated problems like the one above.

Still no response from Cloudflare on my end, anybody have a connection that could escalate my query?

from wgcf.

Could it have anything to do with the 'model' and 'name' attributes for every device under a license? I noticed that the device ID for the 1dot app doesn't have this, whereas the device IDs generated by wgcf have, and possibly CF is using these to tell them apart, and thereby the warp=plus and warp=on, respectively.

Tried that too, as wgcf provides additional args by using --model and/or --name. Does not work for me. What I tried is changing the public key (from the WG Windows app) to CF's API by using my phone's token. It returns warp=plus.

So it looks like there's an issue in connecting the profile with the subscription.

note: I got the beta (no NDAs AFAIK) for both the macOS and Windows app, and I'm experiencing the same issue, returning warp=on. Have contacted them, it's under investigation.

from wgcf.

Thank you for bringing it to their attention, hopefully this time it'll get fixed. I've been having the Android issue for at least a month, changing the status/tick doesn't work for any device.

from wgcf.

I had the same problem.
After adding my warp+ key and running wgcf update, I recreated the wireguard tunnel but kept getting warp=on.
My mistake was not deleting the old .conf file.
So, I deleted the old .conf file, ran wgcf generate, used the new conf file and now im getting warp=plus.
So:

1. Delete old .conf tile
2. Add your warp+ key to the .toml file
3. run wgcf update
4. run wgcf generate
5. A new .conf file should appear, now use that to recreate the wireguard tunnel

from wgcf.

Something is terrible wrong with Cloudflare, I changed my key 3 days ago because all new devices were not getting warp=plus.
It seems one of my old WG configs which I created with my previous key (key that should be disabled because I renewed it) still shows warp=plus.
But If i create new configs on my current key, only warp=on.
I can confirm 101% that something is broken with Cloudflare.

@ViRb3 If you need my previous key which for no reason gets me warp=plus I can share.

C:\Users\plm\Desktop>wgcf_1.0.6_windows_amd64.exe trace
2020/08/03 01:23:25 Using config file: wgcf-account.toml
2020/08/03 01:23:25 Trace result:
fl=50f16
h=cloudflare.com
ip=86.121.121.142
ts=1596407096.136
visit_scheme=https
uag=Go-http-client/2.0
colo=OTP
http=http/2
loc=RO
tls=TLSv1.3
sni=plaintext
warp=plus

C:\Users\plm\Desktop>wgcf_1.0.6_windows_amd64.exe status
2020/08/03 01:23:28 Using config file: wgcf-account.toml
2020/08/03 01:23:29 =======================================
2020/08/03 01:23:29 Device name: RYZEN
2020/08/03 01:23:29 Device model: PC
2020/08/03 01:23:29 Device active: true
2020/08/03 01:23:29 Account type: unlimited
2020/08/03 01:23:29 Warp+ enabled: true
2020/08/03 01:23:29 Premium data: 0
2020/08/03 01:23:29 Quota: 0
2020/08/03 01:23:29 =======================================

C:\Users\plm\Desktop>

Btw, I'm a WARP+ subscriber for 2 months and I use Android.

from wgcf.

I agot an acknowledge from Cloudflare, it's a bug, here is my topic at the CF community: https://community.cloudflare.com/t/getting-warp-on-and-not-warp-plus/202425
I also found that the Windows PC(created using both official beta or using wgcf) in the 1.1.1.1 app on Android can't no longer be saved with the tick as enabled, it automatically disables itself after leaving the devices menu.

It's a pitty, I guess it will take more time to get their bugs ironed out.

from wgcf.

This time they will fix both bugs for real, they already know about these issues, so we sit and pray now.

from wgcf.

The issue is now solved for me, I get warp=plus now.
I think this issue can be safely closed.

from wgcf.

I am verifying the issue now, will keep you updated.

from wgcf.

I can confirm the same issue on my end. Account type is unlimited instead of free, as it should be, but the trace command returns warp=on instead of warp=plus. I updated the API to the newest version in hopes that would fix it, but it didn't change anything. In fact, it seems like the new API breaks the ability to enable/disable active devices from the Account > Manage devices menu, at least on my Android phone - reloading the menu reverts all changes. Could you please confirm? I will be investigating more in the meantime.

from wgcf.

This is what I observe on my end:

`
$ ./wgcf update
2020/07/28 18:39:04 Using config file: wgcf-account.toml

2020/07/28 18:39:06 =======================================
2020/07/28 18:39:06 Device name: F0**BA
2020/07/28 18:39:06 Device model: PC
2020/07/28 18:39:06 Device active: true
2020/07/28 18:39:06 Account type: unlimited
2020/07/28 18:39:06 Warp+ enabled: true
2020/07/28 18:39:06 Premium data: 0
2020/07/28 18:39:06 Quota: 0
2020/07/28 18:39:06 =======================================
2020/07/28 18:39:06 Successfully updated Cloudflare Warp account
$ ./wgcf trace
2020/07/28 18:39:12 Using config file: wgcf-account.toml
2020/07/28 18:39:13 Trace result:
fl=97f269
h=cloudflare.com
ip=177...96
ts=1595972352.934
visit_scheme=https
uag=Go-http-client/2.0
colo=GRU
http=http/2
loc=BR
tls=TLSv1.3
sni=plaintext
warp=on
`
I'm not sure how to change the API, but using the current build binary (1.0.6) Im still able to enable or disable devices using 1.1.1.1 app on my IOS.

from wgcf.

Here's my discoveries so far:

• Whatever I do I can't toggle devices' active status using my Android phone. Whenever I leave the menu and come back to it, nothing has changed. Looking at the network requests confirms that - nothing is being sent on device active toggling. Not sure what's wrong with that.

• I added my WARP+ license key on an iOS device. Frankly, it was able to toggle devices' active status just fine. However, even after multiple experiments, the iOS device did not say warp=plus on the trace page, it remained warp=on no matter the license status. Not sure if this is a bug or just a server-side change, and I don't have another way to test if WARP+ is actually being used.

If somebody has any ideas or any friends at Cloudflare they could ping, please bring them here.

from wgcf.

Probably it is a bug, trace from macOS 10.15.6 (19G73)
2020/07/30 08:53:33 Using config file: wgcf-account.toml 2020/07/30 08:53:33 Trace result: fl=73f109 h=cloudflare.com ip=xx ts=xx.357 visit_scheme=https uag=Go-http-client/2.0 colo=* http=http/2 loc=xx tls=TLSv1.3 sni=plaintext warp=plus

from wgcf.

Is the device from which you purchased your WARP+/Unlimited subscription an Android or iOS? I just tried your exact steps by taking the key from my Android WARP+/Unlimited account and it didn't work.

from wgcf.

Hi, it's an IOS device.
By the way, thank you for your work making this possible

from wgcf.

I tried regenerating and compared the generated conf file... Looks like it doesnt change the privatekey... and I keep having warp=on only when I connect to it... I still guess this is a Cloudflare issue but I don't know how to reach out to them...

from wgcf.

@andrepintorj your private key will only change if you use wgcf v2.0.0+ and execute wgcf update with a new license key. Is your host device an Android or iOS?

from wgcf.

I tried regenerating and compared the generated conf file... Looks like it doesnt change the privatekey... and I keep having warp=on only when I connect to it... I still guess this is a Cloudflare issue but I don't know how to reach out to them...

I just checked, my private key changed. I'm using wgcf v2

from wgcf.

@lt-maker Would you be willing to exchange our license keys for 1 hour, so both of us can test whether they get warp=plus on a new account with the other's key? You can re-generate your key after that, and I will no longer have access. This way we will nail down what could be the cause of it working for you, but not for others.

Here's my e-mail (one-time link), if you could send me your key there and I will reply with mine:
https://privatebin.net/?f93cbb62c35faf90#Dj9wuh8sdy8JV1zF1T5uA5WwCWk79j1dWANBPqG7L7Et

To re-iterate the process, here's what we'll be doing:

• wgcf register a new account. Use a new directory or delete existing .toml file.
• Add the other's license key to your .toml file.
• wgcf update
• wgcf generate
• Use and activate the newly generated profile in WireGuard
• Run wgcf trace and look for warp=plus. Report back here.

from wgcf.

Let me list out what I did exactly till it worked. I started yesterday btw, and just subscibed to warp+ the day before.

1. Downloaded the wgcf binary
2. ran wgcf register
3. ran wgcf generate
4. Entered my warp+ key into the toml file
5. ran wgcf update
6. Created tunnel.

Didnt work, warp=on, then

7. Deleted the .conf file
8. ran wgcf generate
   9 used the new conf file

Worked, warp=plus

from wgcf.

@lt-maker Would you be willing to exchange our license keys for 1 hour, so both of us can test whether they get warp=plus on a new account with the other's key? You can re-generate your key after that, and I will no longer have access. This way we will nail down what could be the cause of it working for you, but not for others.

Here's my e-mail (one-time link), if you could send me your key there and I will reply with mine:
https://privatebin.net/?f93cbb62c35faf90#Dj9wuh8sdy8JV1zF1T5uA5WwCWk79j1dWANBPqG7L7Et

To re-iterate the process, here's what we'll be doing:

• wgcf register a new account. Use a new directory or delete existing .toml file.
• Add the other's license key to your .toml file.
• wgcf update
• wgcf generate
• Use and activate the newly generated profile in WireGuard
• Run wgcf trace and look for warp=plus. Report back here.

Ok

from wgcf.

@lt-maker Would you be willing to exchange our license keys for 1 hour, so both of us can test whether they get warp=plus on a new account with the other's key? You can re-generate your key after that, and I will no longer have access. This way we will nail down what could be the cause of it working for you, but not for others.

Here's my e-mail (one-time link), if you could send me your key there and I will reply with mine:
https://privatebin.net/?f93cbb62c35faf90#Dj9wuh8sdy8JV1zF1T5uA5WwCWk79j1dWANBPqG7L7Et

To re-iterate the process, here's what we'll be doing:

• wgcf register a new account. Use a new directory or delete existing .toml file.
• Add the other's license key to your .toml file.
• wgcf update
• wgcf generate
• Use and activate the newly generated profile in WireGuard
• Run wgcf trace and look for warp=plus. Report back here.

Sent you the key

from wgcf.

@lt-maker I am indeed getting warp=plus with your key. What I noticed is that in wgcf status, your key shows:

2020/07/31 14:02:58 Premium data  : 10000000000

While my key shows:

2020/07/31 14:01:16 Premium data  : 0

So what is this, Cloudflare bug?

from wgcf.

It might be. I just deleted the conf file and regenerated the conf file, now your key shows
2020/07/31 21:08:03 Premium data : 10000000000

It was 0 just before this

from wgcf.

FYI: after upgrading to wgcf 2, deleting the wg profile and running wgcf update then wgcf generate I still dont have the plus.
And my profile shows:
2020/07/31 10:03:57 Account type : unlimited
2020/07/31 10:03:57 Role : child
2020/07/31 10:03:57 Premium data : 0
2020/07/31 10:03:57 Quota : 0

from wgcf.

@lt-maker Indeed, after trying your key, now i get this for every account that I link to my key:

2020/07/31 14:11:09 Premium data  : 10000000000
2020/07/31 14:11:09 Quota         : 10000000000

It's still different from what I get with your key:

2020/07/31 14:10:56 Premium data  : 10000000000
2020/07/31 14:10:56 Quota         : 0

and again different from @andrepintorj's key:

2020/07/31 10:03:57 Premium data : 0
2020/07/31 10:03:57 Quota : 0

I don't know if this has any importance, but it's still weird. I think something is wrong on Cloudflare's end, whether that's simply the text displayed under trace, or the actual WARP+ detection. I will send them an e-mail and keep you updated in this issue.

from wgcf.

Ok, I'll reset my key in 10 mins, is that ok?

from wgcf.

Yes, I am done testing, you can go ahead. Thanks for the help!

from wgcf.

Until a few days ago warp + was connecting to the closest server in my area, now it is connecting to remote servers and is very inefficient. The region I am in, Istanbul, used to connect to Istanbul, now it connects to Romania or Bulgaria. Has anyone had similar problems?

Nope, I'm from Romania and always got Istanbul IP address on WARP from beggining, despite being routed on Bucharest datacenter (I hate google in Turkish because it's weird).
The geo-localization at CF is not accurate, check your latencies before judging the ip location reported by various websites.
Cloudflare does not have an up-2-date geo database on it's IP addreses, if your latencies are low it's just wrong country IP lookup. Check with pings to Turkey IP addreses to make sure, or traceroute. Also add the latency to 1.1.1.1 in the calculation because that should be your overhead VPN latency.

from wgcf.

Until a few days ago warp + was connecting to the closest server in my area, now it is connecting to remote servers and is very inefficient. The region I am in, Istanbul, used to connect to Istanbul, now it connects to Romania or Bulgaria. Has anyone had similar problems?

This issue is not related to the thread here since its how your internet provider routes/peers with Cloudflare. If I were you I'd talk wiith your provider to reevaluate peering with CF.

from wgcf.

Experiencing this issue too. But the weird thing is, I bought a fresh WARP+ subscription recently (5 mins before writing this) on an another Android phone, and it returns warp=plus. Tried using wgcf with the new subscription, it returns warp=on.

Looks like CF has their own method on identifying keys that are generated within 1dot's app and 3rd party apps?

from wgcf.

Could it have anything to do with the 'model' and 'name' attributes for every device under a license? I noticed that the device ID for the 1dot app doesn't have this, whereas the device IDs generated by wgcf have, and possibly CF is using these to tell them apart, and thereby the warp=plus and warp=on, respectively.

from wgcf.

I just tested sharing my Warp+ from my Android to another Android device, the fully official way, and it didn't work. Didn't work to an iPhone either. However it works on iPhone sharing to Android, and even PC. So the issue is definitely on Cloudflare's side. I really hope for a quick resolution. @morpig how did you get in touch with them? I have a couple of questions to ask them, if you could connect me I would really appreciate it.

from wgcf.

I had the same problem.
After adding my warp+ key and running wgcf update, I recreated the wireguard tunnel but kept getting warp=on.
My mistake was not deleting the old .conf file.
So, I deleted the old .conf file, ran wgcf generate, used the new conf file and now im getting warp=plus.
So:

1. Delete old .conf tile
2. Add your warp+ key to the .toml file
3. run wgcf update
4. run wgcf generate
5. A new .conf file should appear, now use that to recreate the wireguard tunnel

Thank you for help

from wgcf.

I just tested sharing my Warp+ from my Android to another Android device, the fully official way, and it didn't work. Didn't work to an iPhone either. However it works on iPhone sharing to Android, and even PC. So the issue is definitely on Cloudflare's side. I really hope for a quick resolution. @morpig how did you get in touch with them? I have a couple of questions to ask them, if you could connect me I would really appreciate it.

There's a helpdesk available from the beta client. It looks like the support system is seperated from general Cloudflare services (does not use support at cloudflare).

They have replied, and acknowledged the warp=on issue. They will fix it within the next couple of days for the official beta, don't know if it applies for 3rd party WG apps.

What questions do you want to ask? Is it about WARP+ routing?

from wgcf.

I managed to get in touch with the Warp development team and I have let them know of this issue. I will keep you updated.

from wgcf.

I as well just received a confirmation that they are aware of the issue and they will address it in a "future release".

from wgcf.

I can confirm this as well, using wgcf trace I get warp=plus. While this took a while to resolve, I am more than happy that I can finally close the issue. If anyone at Cloudflare is reading this - thank you :)

from wgcf.