Tunnels

Yes. With Named Tunnels Open external link you can create a CNAME at the apex that points to the named tunnel.

Cloudflare offers two modes of setup: Full Setup, in which the domain uses Cloudflare DNS name servers, and Partial Setup (also known as CNAME setup) in which the domain uses non-Cloudflare DNS servers.

The best experience with Cloudflare Tunnel is using Full Setup because Cloudflare manages DNS for the domain and can automatically configure DNS records for newly started Tunnels.

You can still use Tunnel with Partial Setup. You will need to create a new DNS record with your current DNS provider for each new hostname connected through Cloudflare Tunnel. The DNS record should be of type CNAME or ALIAS if it is on the root of the domain. The name of the record should be the subdomain it corresponds to (e.g. example.com or tunnel.example.com) and the value of the record should be subdomain.domain.tld.cdn.cloudflare.net. (e.g. example.com.cdn.cloudflare.net or tunnel.example.com.cdn.cloudflare.net)

Tunnel can expose web applications to the internet that sit behind a NAT or firewall. Thus, you can keep your web server otherwise completely locked down. To double check that your origin web server is not responding to requests outside Cloudflare while Tunnel is running you can run netcat in the command line:

$ netcat -zv [your-server’s-ip-address] 80
$ netcat -zv [your-server’s-ip-address] 443

If your server is still responding on those ports, you will see:

[ip-address] 80 (http) open

If your server is correctly locked down, you will see:

[ip-address] 443 (https): Connection refused

No. When using Cloudflare Tunnel, all requests to the origin are made internally between cloudflared and the origin.

To log external visitor IPs, you will need to configure an alternative method Open external link .

​​ Ensure that only one instance of cloudflared is installed as a service

If you are unable to create a Tunnel using the installation script (“cloudflared service is already installed”), ensure that no other cloudflared instances are running as a service on this machine. Only a single instance of cloudflared may run as a service on any given machine. Instead, we recommend adding additional routes to your existing Tunnel. Alternatively, you can run sudo cloudflared service uninstall to uninstall cloudflared.

​​ Check your DNS records

If you are unable to save your Tunnel’s public hostname (“An A, AAAA, or CNAME record with that host already exists”), choose a different hostname or delete the existing DNS record. Check the DNS records for your domain from the Cloudflare dashboard Open external link .

​​ Run Tunnel with debug logging

If you created a Cloudflare Tunnel from Zero Trust, the tunnel runs as a service on your OS. You can modify the Cloudflare Tunnel service with one or more configuration options. To learn more, refer to our remote management documentation.

​​ Run Tunnel with debug logging

Use the following command to run your Tunnel in the debug mode:

$ cloudflared tunnel --loglevel debug run

The --loglevel flag indicates the logging level, which can be one of {debug, info, warn, error, fatal} (default: info). At the debug level, cloudflared will log and display the request URL, method, protocol, content length, as well as all request and response headers. However, please note that this can expose sensitive information in your logs.

​​ Check SSL/TLS encryption mode

1. On the Cloudflare dashboard for your zone, navigate to SSL/TLS > Overview.
2. If your SSL/TLS encryption mode is Off (not secure), make sure that it is set to Flexible, Full or Full (strict).

When the encryption mode is set to Off (not secure), you may encounter connection issues when running a Tunnel.

​​ Check location of credentials file

If you encounter the following error when running a Tunnel, double check your config.yml file and ensure that the credentials-file points to the correct location. You may need to change /root/ to your home directory.

$ cloudflared tunnel run
2021-06-04T06:21:16Z INF Starting tunnel tunnelID=928655cc-7f95-43f2-8539-2aba6cf3592d
Tunnel credentials file '/root/.cloudflared/928655cc-7f95-43f2-8539-2aba6cf3592d.json' doesn't exist or is not a file

​​ I am having an issue with a locally-managed tunnel.

Before contacting the Cloudflare support team:

• Take note of any specific error messages and/or problematic behaviors.

• Take note of any options you specified, either on the command line or in your configuration file, when starting your tunnel.

• Set log-level to debug, so the Cloudflare support team can get more info from the cloudflared.log file.

• Set transport-loglevel to debug.

• Include your Cloudflare Tunnel logs file (cloudflared.log). If you did not specify a log file when starting your tunnel, you can do so using the logfile option either on the command line or in your configuration file.

• Include your full config.yml file for the affected tunnel.

• Make sure that the cloudflared daemon is updated to the latest version Open external link .

• Gather any relevant error/access logs from your server.