cloudflare / cloudflare/cloudflared

trycloudflare.com blocked by McAfee

Open
#629 3 comments 0 reactions 0 assignees View on GitHub
Needs clarification Type: Bug
Dominant language
Go
Stars
15.6k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**

```
docker run -it cloudflare/cloudflared tunnel --url 0.0.0.0:8080
Unable to find image 'cloudflare/cloudflared:latest' locally
latest: Pulling from cloudflare/cloudflared
b170a134a788: Pull complete
b90f56cb3beb: Pull complete
ee3f4afae713: Pull complete
Total: [==================================================>] 24.15MB/24.15MB
Digest: sha256:c1ea6e495089d21539f915c2b16ca1e96bcdd3cd082c7af6198b70a1ce34d4c3
Status: Downloaded newer image for cloudflare/cloudflared:latest
2022-04-21T10:29:55Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
2022-04-21T10:29:55Z INF Requesting new quick Tunnel on trycloudflare.com...
failed to request quick Tunnel: Post "https://api.trycloudflare.com/tunnel": x509: certificate is valid for *.safezone.mcafee.com, safezone.mcafee.com, not api.trycloudflare.com
```

The hardware is on a home network, using a CenturyLink modem. CenturyLink modems include McAfee security by default (https://www.centurylink.com/home/help/internet/security/mcafee.html). It seems McAfee have the `trycloudflare.com` blacklisted, and instead of reaching the CloudFlare services, the requests are getting blocked by the security system. Presumably these McAfee blacklists are used more widely than just home routers, so likely has implications on other more production networks and systems too.

Outside of this network, without these routers, I get:

```
curl api.trycloudflare.com
{"success":false,"result":null,"errors":[{"code":10002,"message":"GET /"}]}%

curl api.trycloudflare.com -I
HTTP/1.1 400 Bad Request. <-- I see this as a positive, this is CloudFlare responding.
Date: Thu, 21 Apr 2022 10:53:23 GMT
Content-Type: application/json
Content-Length: 76
Connection: keep-alive
Server: cloudflare
CF-RAY: 6ff5935bcab688ad-LHR
```

Inside/behind McAfee, no response:

```
root@rr:~# curl api.trycloudflare.com
root@rr:~#
```

```
root@rr:~# curl api.trycloudflare.com -I
HTTP/1.1 302 Found
Date: Thu, 21 Apr 2022 10:52:41 GMT
Server: SHP
Referrer-Policy: no-referrer
X-XSS-Protection: 1; mode=block
X-Frame-Options: DENY
Content-Security-Policy: default-src 'self' http://shgw.router:8080 stats.g.doubleclick.net www.google-analytics.com analyticsdcs.ccs.mcafee.com *.mcafee.com https://websdk.moengage.com https://inapps.moengage.com https://cdn.moengage.com; script-src * 'unsafe-inline' 'unsafe-eval'; style-src * 'unsafe-inline' 'unsafe-eval'
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
Location: http://blockpg-dock.safezone.mcafee.com/blockpage/redirect/?ctxt=Kzd5WVBCL0JWS0lTS0c0YWo4Z1RWQndFbU9kWWhTTlQzVG82OWtUa3NHUlhHbEZhY3RIb0UwM25ZaVY3QmlNaFFmRFpYZFg1R045bGcwU3FFZHlGeEt3PQ==&ts=1650538361
Connection: close
Content-Type: text/html; charset=UTF-8
```

```
root@rr:~# curl api.trycloudflare.com -L

SHP Redirector












```

**Expected behavior**
Cloudflared test tunnel to come up.

**Environment and versions**
- OS: Intel NUC
- Architecture: MACHINE="genericx86-64"

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.