Hello. Please correct me if I am reading wrong, but does this PR essentially add a link to yours/somebody else's WARP+ profile? If that is the case, while I appreciate the good intentions, this is not something I am willing to merge, for a couple of reasons. It's probably against Cloudflare's Terms of Service, it's bad for privacy to share somebody else's account, and it doesn't actually resolve the problem with no WARP+. If you could direct all people who have this problem to post an issue here on GitHub, I will be more than happy to look into this.

If that's the case, then we will change the readme again giving the instructions on how to fix the WARP+ issue.
In that case, people can use their own license key.

Do you have a fix for the WARP+ issue? Is it removing the IPv6 from AllowedIPs? I thought the IPv6 part only fixed reCaptcha on some websites.

We've confirmed yesterday that even after changing the license key, the displayed status will just be warp=on instead of warp=plus. But we managed to find a simple way to work around this issue without any coding needed.
Also for some reasons, removing the IPv6 from the AllowedIPs can fix the Unusual traffic from your computer network reCAPTCHA on Google Search. But people can just add the IPv6 back if they prefer to use it.

But we managed to find a simple way to work around this issue without any coding needed.

What is the workaround? Telling people to use your WARP+ profile instead of theirs? If that is the case, my previous statement remains. But if you have found another workaround, I am happy to hear about it. Apologies for any miscommunication.

I've changed the README.md and ready to create another PR or you can add it to the file yourself. It's up to you.

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

7. After running the command, connect using WireGuard
8. While connected, run this command to see if it works as expected

wgcf trace

9. 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.

Ah, I see. Very interesting. I will move this discussion in a GitHub issue and post your workaround there. I will try to reproduce the problem and fix it properly the next few days. If anybody else experiences this, post in the issue as well.