# Cloudflare Tunnel gets a trial live while IT's port ticket waits

> Outbound-only connections are an easier ask of security teams, but a published hostname stays open to the whole internet until an Access policy guards it.

Original: https://fdetimes.net/en/tools/cloudflare-tunnel-client-trial-no-inbound-ports/

The demo is already running on a virtual machine inside the client's network. The business users want to try it this afternoon. But the ticket asking IT to open an inbound port is still sitting in the queue. It might wait a week, or it might be rejected outright.

Every FDE has been stuck at this exact point. Cloudflare Tunnel gets around it. Instead of waiting for outside traffic to come in, the client's machine calls out. Cloudflare's official documentation describes the tool as a way to connect your resources to Cloudflare without a publicly routable IP address.

This is not a trick for infrastructure enthusiasts. Knowing how to use it means the trial happens this week instead of next month, and on an engagement that difference is large.

## Why is going out easier than coming in?

The core component is cloudflared, a server-side daemon that connects your infrastructure to Cloudflare. According to the documentation, Tunnel uses an outbound-only connection model that still allows two-way communication. A user's request reaches Cloudflare, then travels back along the connection that cloudflared has already opened.

That means the client's firewall can allow only these outbound connections and block all inbound traffic. For a security team, this is a far lighter request than "open port 443 to VM X".

Cloudflare's 2021 announcement, from when the product was still called Argo Tunnel, put it plainly: your team no longer needs to punch holes in the firewall, and from then on outbound-only connectivity was free for every organisation.

One detail is easy to miss. "Outbound only" does not mean you never need to ask IT anything. The documentation requires the server to reach Cloudflare outbound on port 7844, and you should check this before going further. Many corporate networks restrict egress too, so this is the first question to take to your meeting with IT.

## A trial, step by step

Suppose you need to give 15 people in the client's operations team access to an internal agent. Step one is to confirm with IT that the VM can reach port 7844 outbound. It is a question about egress, not a request to change the firewall.

Step two is to create the tunnel in the dashboard. Following the guide, you choose the operating system, copy the installation command provided, run it in a terminal on the origin server and wait for the tunnel to report that it is connected. Each tunnel opens four connections to four different servers in at least two data centres, so a single point of failure on Cloudflare's side will not take down your demo.

Step three is to publish a hostname that points to the service. Stop here. The documentation is explicit: from this moment, anyone on the internet can reach the application at that hostname. An agent that reads the client's internal data, left open like this, is a security incident, not a trial.

**Key point:** Opening a way in is not enough; the real question is who is allowed through.

Step four is therefore mandatory: attach Cloudflare Access. Access decides who can reach the application based on the policies you configure, and it denies by default. For those 15 people, the policy should allow only their email addresses. The right order is to attach the policy first and send the link second, never the other way round.

## Quick Tunnel, and when it lets you down

Cloudflare also offers Quick Tunnel, which needs neither an account nor a domain. For showing a colleague a build for ten minutes, it is very handy. For a serious trial, its limits show up fast.

Each Quick Tunnel handles at most 200 concurrent in-flight requests, and it does not support SSE. A limit of 200 sounds generous for 15 people. The problem is SSE: many LLM chat interfaces stream answers token by token over SSE, so your agent can work fine on your own machine and freeze the moment the client opens the link.

The SSE limit alone is reason enough to keep Quick Tunnel for throwaway demos. A trial on real data should go through a tunnel created in the dashboard, where you can attach an Access policy as in step four.

## What to learn first, and how to tell the story

Do not start with syntax. Learn the model: which connection goes out, which path the request takes back, and which layer decides access. Anyone who grasps those three things can explain them to the client's security team, and that is the hard part of the job.

Then practise at home on any service: set up a tunnel, publish a hostname, lock it with Access so only your email gets in, then open the link in an incognito window to make sure strangers are blocked. The exercise takes one evening, but it teaches you the exact sequence you will use on a real client site.

On your CV or in an interview, do not write "knows Cloudflare". Tell the problem: the system ran on-prem, IT would not open inbound ports, and you gave users a trial through outbound-only connections with an allow-list access policy. An FDE hiring manager hears someone who understands client constraints, not just someone who knows a tool.

Next time a port-opening ticket stalls, do not sit and wait for it. Start with a different question for IT: can the server reach Cloudflare outbound on port 7844?

**Try this week:**

- Ask the client's IT team the first question: can the server reach Cloudflare outbound on port 7844?
- Set up a tunnel in the dashboard for a service running on your machine, attach an Access policy that allows only your email, then open the link in an incognito browser to test it.
- Rewrite one line of your CV to describe exactly how you gave a client a trial of an on-prem system without opening any inbound ports.

## Sources

- [Cloudflare Tunnel (Cloudflare Docs)](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/)

- [A Boring Announcement: Free Tunnels for Everyone](https://blog.cloudflare.com/tunnel-for-everyone/)

- [Create a tunnel (dashboard)](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/)

- [Policies (Cloudflare Docs)](https://developers.cloudflare.com/cloudflare-one/policies/access/)

- [Tunnel availability and failover](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/)

- [Quick Tunnels (Cloudflare Docs)](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/do-more-with-tunnels/trycloudflare/)
