v2.3

• Fix for activation via new protocol [F11]
• RPM packages for Mageia-9

Note: To activate warp in Russia, it is most advisable to use a VPN connection SSTP, IKEv2/IPsec or L2TP/IPsec.

v2.2.1

• Added new activation protocol (F11 button)
• RPM packages for Mageia-9

Note: It is too early to use this release, since the Cloudflare (TM) WARP feature is in testing mode: the transition back from the new protocol to the old one may not work (an update is required). However, if you really need it, then use it. For activation (Russia, Iran (?), China (?), etc.), it is most appropriate to use SSTP, IKEv2/IPsec or L2TP/IPsec.

If activation was unsuccessful, change VPN and try again. In the mode with the new protocol, the endpoint is selected automatically (no need to press F12).

Tested in Mageia-9 with network/net_applet and NetworkManager/nm-applet (see ScreenShots.tar.gz).

v2.2

• warp-cli: "warp-stats" command deprecated; "tunnel stats" instead
• RPM packages for Mageia-9

Note: Don't forget to update Cloudflare (TM) WARP to the latest version (F2 button)

v2.1

• warp-cli: the "register" command deprecated; "registration new" instead
• warp-cli: the "reset-settings" command deprecated; "settings reset" instead
• warp-cli: the "set-custom-endpoint" command deprecated; "tunnel endpoint set" instead
• warp-cli: the "clear-custom-endpoint" command deprecated; "tunnel endpoint reset" instead
• RPM packages for Mageia-9

Note: Don't forget to update Cloudflare (TM) WARP to the latest version (F2 button)

v2.0

• /usr/bin/warp-update: added forced systemctl restart warp-svc
• RPM packages for Mageia-8 and Mageia-9

Description: cloudflare-warp-2023.9.301rpm package contains an incorrect script after updating.

Note: Around March 2024, Cloudflare (TM) WARP in Russia may be permanently blocked. It is highly recommended to switch to the XTLS-Reality protocol and use XRayGUI - for individual protection or to SocksGW - to protect your families. Good luck.

v1.9

• Fixing /bin/warp-update
• Packages for Mageia-8/9

Note: After updating the package, don't forget to update cloudflare-warp (F2 key in warpgui window)

I remind you, if registration is not possible in your country (status: registration attempt...), - close warpgui, start any VPN connection (OpenVPN/WireGuard), open warpgui and wait 3-5 seconds. After changing the status from registration attempt... to waiting for connection..., disable the VPN, it is no longer needed. If there is no connection after registration (status: waiting for connection...), press [F12] sequentially, with an interval of 3-5 seconds, until the connection is established. Good luck.

v1.8

• Improving the updater [F2]
• Compatible with ROSA Linux
• Packages for Mageia-9 and ROSA-12.3 (*.mrx8)

Note: To use in ROSA Linux, you need to install rosa-resolver-patch

v1.7

• Automatic installation of cloudflare-warp [F2]
• RPM packages for Mageia-9 (Mageia-8 is unstable)

v1.6

• cloudflare-warp package required (spec)
• RPM packages for Mageia-9 (Mageia-8 is unstable)

Note: Since Cloudflare (TM) WARP is now being updated from its own repository, before installing warpgui-v1.6, delete the previous version, install the repository and the cloudflare-warp package (under su):

curl -fsSl https://pkg.cloudflareclient.com/cloudflare-warp-ascii.repo | tee /etc/yum.repos.d/cloudflare-warp.repo && dnf update && dnf install -y libcap-utils && dnf install -y cloudflare-warp

...and install warpgui-v1.6.

v1.5

• warp-cli 2023.3.258 - Belated status Connecting/Connected
• warpgui: Exclude network analysis by warp-cli status
• Release for Mageia-8, Mageia-9 and LUbuntu-22.04

Attention! Since warp-cli version 2023.3.258, incorrect operation has been noted on Linux systems using systemd-resolved (for example, ROSA Linux): warp-cli spontaneously resets its own nameservers from /etc/resolv.conf and disconnects the network! On systems with resolvconf (Mageia Linux), warp-cli works fine.

URL for your offers: https://github.com/cloudflare/cloudflare-docs