CF_HAPPY_EYEBALLS_MITM_FAILURE or “Unable to Connect” in Cloudflare WARP: Fix

Cloudflare logo

Short answer: “Unable to connect, Connection blocked” with error CF_HAPPY_EYEBALLS_MITM_FAILURE means something on the network you are using (usually the router or a firewall) is blocking the traffic Cloudflare WARP needs. Open WARP’s settings, choose Reset Encryption Keys, then turn WARP off and on again. If it still fails, choose Re-Authenticate Session and sign in with your work Microsoft account. The same re-authenticate step also fixes most “Access restricted. This site is blocked” pages for work systems you should be able to reach.

A migration agency contacted us because one of their staff, working from overseas, could not reach the office’s remote desktop server. Her laptop connected perfectly on her phone’s hotspot, but on her home Wi-Fi the Cloudflare WARP window turned red with “Unable to connect” and “Connection blocked”. Restarting the laptop had not helped. We sent her two quick steps to reset WARP’s encryption keys and, if needed, re-authenticate her session. Within the hour she replied that it was fixed. A similar re-authentication also restored access for an engineer whose work cameras and control systems suddenly showed “Access restricted” when he connected from home. Here is what these errors mean and how to fix them.

Fixed by Rohan Colley, Senior Systems Administrator at GCIT, and the GCIT service desk team. Written up by Elliot Munro, CISO.

Symptoms

When you connect Cloudflare WARP (the Zero Trust client in your system tray or menu bar), the toggle stays on but the window shows:

Zero Trust
Unable to connect
Connection blocked
Error: CF_HAPPY_EYEBALLS_MITM_FAILURE
WARP is unable to reach its destination. Try rebooting your router or contact your administrator to make sure all third-party security tools allow WARP ingress IPs and ports.

Cloudflare WARP Zero Trust window: Unable to connect, Connection blocked, Error CF_HAPPY_EYEBALLS_MITM_FAILURE

Typical signs:

  • It works on a mobile hotspot or in the office, but not on one particular network, such as home Wi-Fi, a hotel or a café.
  • Remote desktop, mapped drives or internal web apps that go through WARP stop working.
  • Remote Desktop may only say “There was a problem connecting to the remote resource. Ask your network administrator for help.” In two of our cases this simply meant WARP was not connected, so the connection never reached the office server.
  • Normal internet browsing may or may not still work.

A related problem: WARP connects, but when you open a work system you should have access to, the browser shows a Cloudflare page instead:

Access restricted
This site is blocked. Please contact your administrator for further assistance.

Cloudflare Gateway block page: Access restricted. This site is blocked. Please contact your administrator for further assistance.

People search for these as “CF_HAPPY_EYEBALLS_MITM_FAILURE”, “Cloudflare WARP unable to connect connection blocked”, “WARP works on hotspot but not home Wi-Fi”, “Zero Trust unable to connect” or “blocked by Cloudflare Gateway access restricted”.

Affected Software

  • Application: Cloudflare WARP client (Cloudflare One / Zero Trust), used for secure remote access to office systems and for web filtering
  • Platform: Windows and macOS (the same errors appear on the mobile apps)
  • Related Services: Cloudflare Gateway (filtering and access policies), Microsoft Entra ID sign-in for Cloudflare Access

Cause

“Unable to connect”. WARP builds an encrypted tunnel to Cloudflare using UDP traffic on specific ports. Cloudflare’s documentation says CF_HAPPY_EYEBALLS_MITM_FAILURE means a router, firewall, antivirus program or other security product is blocking UDP on the WARP ports. Some home routers, ISP filters, public Wi-Fi networks and national firewalls in some countries interfere with this traffic, which is why the same laptop works on a phone hotspot. A stale set of encryption keys on the device can produce the same symptom after a network change.

“Access restricted”. Your organisation’s Cloudflare policies decide which work systems each person can reach, often based on your Microsoft 365 group membership. WARP reads that membership when you sign in. If you were added to a group recently, or your session is old, WARP may still be using out-of-date information and block a system you are now allowed to use. In the case above, the engineer’s group membership had not been read properly until his session was refreshed.

Resolution

Step 1: reset the encryption keys

  1. Click (on Mac) or right-click (on Windows) the Cloudflare WARP icon in the system tray or menu bar, then click the settings cog and open Preferences.

    Cloudflare WARP Zero Trust window with the settings cog highlighted in the bottom right corner

  2. Select Connection, then Reset Encryption Keys. It takes about five seconds and tells you when it has finished.
  3. Turn the WARP toggle off, wait a few seconds, and turn it back on.

Step 2: re-authenticate your session

  1. If the error is still there, or you see “Access restricted” for a work system, open Preferences again.
  2. Select Account, then Re-Authenticate Session.
  3. When the browser opens, choose your organisation’s Microsoft (Azure AD) sign-in and sign in with your work account and MFA.
  4. Reconnect WARP and try the system again.

Depending on your WARP version, these options may appear as Settings, Advanced or Preferences, but the wording of the buttons is the same.

Step 3: if it still will not connect

  1. Restart your home router and try again.
  2. Try a different network, such as your phone’s hotspot, to confirm the problem is the network rather than the laptop.
  3. Contact your IT team. Tell them the exact error code, which network it fails on, and whether a hotspot works. They can check the device is still enrolled and, if needed, change how WARP connects so it works on networks that block its usual traffic.
  4. If WARP will not reconnect at all, your IT team may need to repair or reinstall it and sign it back in to your organisation. For one overseas user, reconnecting and a repair both failed, and a reinstall restored the tunnel and Remote Desktop straight away. For another user, restarting the WARP service and reconnecting worked, but the problem came back later the same day, so tell IT if it keeps happening rather than repeating the same fix.

Important Notes

  • Do not turn WARP off to get around the problem. On a managed device that removes the protection and filtering your organisation relies on, and work systems will not be reachable anyway.
  • A blocked site is not always a fault. “Access restricted” also appears for websites your organisation blocks on purpose, such as malicious or unsafe categories. If it is a website rather than a work system, ask your IT team to review it rather than trying another browser.
  • Do not reinstall WARP as a first step. Reinstalling rarely fixes a blocked network and can remove your organisation’s enrolment settings.
  • Travelling overseas? Networks in some countries block VPN style traffic. Test your connection before you rely on it for urgent work, and tell your IT team where you will be.

If remote access for your team keeps dropping out, book a free consultation with our team.

Was this article helpful?
Ready to secure and simplify your IT? Talk to a GCIT expert today.