After updating to 2024.12.554 [Windows] WARP service is no longer available

What is the name of the domain?

example.com

What is the error message?

The Cloudflare WARP service is not available. Try rebooting.

What is the issue you’re encountering

UI and CLI apps can’t connect to the service. Service is stuck in an infinite restart loop because requests to https://api.cloudflareclient.com./v0/reg/ keep timing out.

What steps have you taken to resolve the issue?

Tried disabling Windows firewall.

Tried resolving hostname and pinging api.cloudflareclient.com - both worked correctly.

Tried manually sending a get request to the same URL. It returned a 401 status (expected), but not a timeout. It seems like my machine is able to contact and send requests to the client registration endpoint, but WARP service can’t.

I ran warp-diag. IPv4 connectivity is non-functional (as expected, country has been trying to block WARP for years now), IPv6 seems functional.

Relevant part of the warp service log file looks like this:
2024-12-21T07:46:53.375Z DEBUG main_loop: warp::storage::registration: Error loading registration config, fetching a new one
2024-12-21T07:46:53.575Z DEBUG main_loop: warp_api_client::addresses: Caching initial API IPs consumer=[104.16.80.230, 104.17.143.163, 2606:4700::6811:8fa3, 2606:4700::6810:50e6] teams=[162.159.138.105, 162.159.137.105, 2606:4700:7::a29f:8969, 2606:4700:7::a29f:8a69]
2024-12-21T07:46:53.576Z DEBUG main_loop: warp_api_client::apis::registration: Getting registration registration_id=Client(ConsumerRegistrationId(my_token))
2024-12-21T07:46:53.576Z DEBUG main_loop: warp_api_client::client: Sending API request GET https://api.cloudflareclient.com.//v0/reg/my_token
2024-12-21T07:46:54.378Z WARN watchdog: warp::watchdog: Watchdog reports hung daemon watchdog_name=“main loop” hang_count=1 hang_tick=1
2024-12-21T07:46:54.393Z ERROR actor_device_state::handler: Failed to collect device state information. err=ActorStateRequestFailed(RequestTimedOut)
2024-12-21T07:46:55.386Z WARN watchdog: warp::watchdog: Watchdog reports hung daemon watchdog_name=“main loop” hang_count=1 hang_tick=2

2024-12-21T07:47:03.460Z WARN watchdog: warp::watchdog: Watchdog reports hung daemon watchdog_name=“main loop” hang_count=1 hang_tick=10
2024-12-21T07:47:03.584Z ERROR main_loop: warp_api_client::client: API request error ReqwestError(reqwest::Error { kind: Request, url: “https://api.cloudflareclient.com./v0/reg/my_token”, source: TimedOut }), retrying in 1.208738403s
2024-12-21T07:47:04.470Z WARN watchdog: warp::watchdog: Watchdog reports hung daemon watchdog_name=“main loop” hang_count=1 hang_tick=11

2024-12-21T07:47:24.608Z ERROR watchdog: warp::watchdog: Process has been hung for too long, restarting it manually
2024-12-21T07:47:24.609Z ERROR warp::warp_service: Watchdog is shutting down an overly hung daemon.

And the service is just stuck in this restart loop until I manually stop it.

Screenshot of the error

Forgot to mention that I did try to rollback to previous versions. It did not help.
Versions I tried: 2024.8.458 2024.11.309 2024.12.492

I have the same problem :frowning:

There is such a topic WARP client version 2024.12.554.0 fails to connect to WARP - #3 by user11666
Rollback to 492 connects very poorly, I haven’t rolled back to 390 yet, but I think so. So the IPv6 network disappeared, most likely the problem is not with the client.

I can’t open app after update/reinstall. i have this image. rollback Windows can’t help.

In general, switching to version pkgver = 2024.11.309 solves the problem + IPv6 appears. For Manjaro I used GitHub - AKotov-dev/warpgui: GUI for Cloudflare ™ WARP and not GitHub - progzone122/warp-cloudflare-gui-rust: A GUI application based on warp-cli for linux written in Rust, then they will connect fine.
And also, I used a VPN to reset the F11 account, turned off the VPN after registering again and then connected to WARP

First method from this video helped me