CF Managed Network Endpoint

CF Managed Network Endpoint is a lightweight TLS (Transport Layer Security) endpoint for Cloudflare Zero Trust Managed Networks that serves a stable…

  • Network Services
  • Security
CF Managed Network Endpoint is a lightweight TLS (Transport Layer Security) endpoint for Cloudflare Zero Trust Managed Networks that serves a stable self-signed certificate on port 6443, letting Cloudflare WARP clients identify home-network devices.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

45/100 Fair

Maintained
84last commit 24 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-10-28
Latest release
v1.0.9
License
MIT
Activity
rising

Checked 23 days ago - source: GitHub (Tom-Joad/cf-managed-network-endpoint)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 4 CPU core(s).

Checked 46 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fingerprint stability Keep the Config/appdata folder (keys/) backed up and never delete the generated certificate. If it is lost, a new fingerprint is created and WARP home-network detection breaks silently. The fingerprint is printed in container logs on each start. source
  • Network setup If Cloudflare Managed Networks is configured for a VLAN (virtual LAN), create the matching host interface first, for example br0.10. source
  • Upgrading from before 1.0.0 Keep the old /certs path mapped for the first start so the existing certificate is reused, then remove it. source

Fetched 44 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which folder should I back up to keep the Cloudflare fingerprint stable?

Back up the persistent config volume, including /config/keys where cert.crt and cert.key are stored. If that folder survives, the fingerprint remains the same across restarts and updates.

What happens if I delete the certificate folder?

The container will create a new certificate with a new fingerprint, and Cloudflare managed-network detection can break silently. If only one of the two key files exists, it aborts instead of creating a new pair.

Which port does the endpoint need?

It serves the TLS endpoint on port 6443. With a custom VLAN interface, the container listens on its own IP and no port mapping is needed.

When does the Cloudflare client recheck for managed networks?

It scans when the OS default route changes, the active Wi-Fi SSID changes, or the DNS servers of the default interface change.

Do I need a separate endpoint for every home location?

No, Cloudflare says to reuse the same TLS endpoint across multiple locations to minimize performance impact.

Answers sourced from developers.cloudflare.com, github.com

Community

Collected 44 days ago - public community threads