ViRb3
Internet access does not work (abuse prevention)
0 B received. Handshake did not get completed.
I thought it could be account issue. Registered a new account from a VPN and tried connecting with the new config.
Still same.
Edit from maintainer:
Just to give some organization to all the "internet does not work" reports. There are two known cases when this may happen:
- If the WireGuard tunnel works on your other computer/phone, but not on this one, then it's likely an issue with your system configuration. It's generally not something I can help with, as wgcf is only responsible for providing you with a WireGuard profile, but leaving this issue open for people to share their experiences and solutions. This is tracked in #50.
- If the WireGuard tunnel does not work on any of your devices, but the official client does, then this is likely an issue with your region being restricted due to abuse prevention. There is no solution to this problem, maybe hope that people stop abusing the service so the regions are unlocked. Use the official client in this case. This is tracked in #158.
Thanks for the swift response. I checked there before posting this. I'm on windows. I don't think whatever I'm facing is related to that thread.
It was working fine until an hour back and never had an issue since I started using this for about 2 months.
My general response would be to test this on a fresh Ubuntu 21.10 installation and see if it works there. If not, it's definitely an issue with your Windows installation. Otherwise, could be a ton of different things that guessing would be impossible. FWIW, everything works fine here on macOS and Ubuntu.
got ya. thanks. I'll check it out. But it is weird that it was working fine until an hour back.
So I don't think it is a windows issue.
I am facing the same issue here. It suddenly stopped working an hour or two ago.
wgcf suddenly stopped working today all over, it's not windows fault, looks like cloudflare banned it
I can confirm the issue, just started happening to me on macOS too. Will try to investigate soon.
@AdroitAdorKhan @Juancollado2003 are you guys on windows too?
Windows 10, Debian 11, Android 11 & RouterOS 7.x. Confirmed, not working anywhere since last 2 hours (maybe).
I can confirm the issue, just started happening to me on macOS too. Will try to investigate soon.
Could be CF changed host address or port?
I'm not sure if this is anyway related.
Cloudwarp windows client works fine for me. So I tried capturing traffic using wireshark to see if there is any difference in packets.
What caught my eye was, there is a field called wg.reserved which has value b91981 in all "wireguard protocol" traffic via warp client.
For the traffic via wireguard client, this value is 000000
I can confirm the issue, just started happening to me on macOS too. Will try to investigate soon.
Could be CF changed host address or port?
Port seems to be the same. Native warp client uses a different IP. I tried with that as well. But it didn't help
I also encountered this problem, and I noticed that I could get a response from the end of the 6in4 tunnel, but warp showed that all the services that depended on it offline were down.
I thought the 6in4 tunnel of HE was broken. I tried to dial again many times and checked the server status page of HE. I noticed that I could get from the opposite end of the 6in4 tunnel. Everything was fine when I only used 6in4.
This is weird, I'm using WARP on a Mikrotik router, stopped working 3-4 hours ago. So this is not OS related, it must be server related. Basically i get no RX packets and no handshakes.
I have just received an unofficial response from Cloudflare. Indeed, unofficial clients like WireGuard are blocked server-side due to huge amount of abuse. Exactly what form of abuse I do not know. However, the block is expected to be lifted later today, and I am working with them on a long-term solution. For now though:
:warning: Please do not use wgcf to abuse Cloudflare WARP. If wgcf allows you to do something different from using WARP on unsupported devices, please stop. Doing so will get all of us banned permanently.
prepare for the worst, use the warp-cli for linux or official clients for windows/macos.
since the beginning cloudflare never supports unofficial clients or use own wg config for WARP, so don't cry if they block it again...
First time trying out wgcf but I have no internet. No idea if it's my setup or it's being block again.
Get "https://api.cloudflareclient.com/v0a1922/reg/aa72d4c8-f9b6-41ba-849f-667451dfec47": dial tcp: lookup api.cloudflareclient.com on [::1]:53: read udp [::1]:35982->[::1]:53: read: connection refused
Using Fedora Silverblue with nmcli
Now, it is working!
Hi, did you change anything?? still doesn't work for me
Now, it is working!
Hi, did you change anything?? still doesn't work for me
It seems to be region related, I tested Tokyo's network already works, but Hong Kong's still doesn't.
Doesn't work for me either. Works with official app. I used to config the NetworkManager with this config in linux. Which also stopped working for few days. This is the error I get.
./wgcf register
2022/03/07 05:52:48 Using config file: wgcf-account.toml
This project is in no way affiliated with Cloudflare
Cloudflare's Terms of Service: https://www.cloudflare.com/application/terms/
✔ Yes
2022/03/07 05:52:49 Post "https://api.cloudflareclient.com/v0a1922/reg": dial tcp: lookup api.cloudflareclient.com on [::1]:53: read udp [::1]:36907->[::1]:53: read: connection refused
I'm not sure if this is anyway related.
Cloudwarp windows client works fine for me. So I tried capturing traffic using wireshark to see if there is any difference in packets.
What caught my eye was, there is a field called wg.reserved which has value b91981 in all "wireguard protocol" traffic via warp client.
For the traffic via wireguard client, this value is 000000
That's Cloudflare's clientid, which is used for routing.
Does cloudflare plan to set some restriction for users this days? i even can not connect server properly using official Android APP
I can connect via the official Windows client though.
neither can Android app nor window client connect successfullyðŸ˜ðŸ˜