Specific server providers setups ‐ Cloudflare - MarechJ/hll_rcon_tool GitHub Wiki

🧭 You are here : Wiki home / Additional Setup / Specific server providers setups / Cloudflare


Setting up Cloudflare's cloudflared

The following guide will help you setup Cloudflare's Zero Trust application service tunnel called cloudflared. Typically this is used to secure internal applications using the Zero Trust authentication system, of which you can utilize Google/Microsoft authentication.

Another reason is to expose your applications from within your home network where your service provider might block port 80/443.

1. Sign up for Cloudflare

You'll need a Cloudflare account, and you will also need a domain name setup on cloudflare.

Ensure you have access Zero Trust section so that it's setup in your account.

2. Add cloudflared to compose.yaml

The cloudflared service needs to be configured in your compose.yaml file.

tunnel:
    container_name: cloudflared-tunnel
    image: cloudflare/cloudflared
    restart: unless-stopped
    command: tunnel run
    environment:
      - TUNNEL_TOKEN=mytokengoeshere

3. Configure Application on Cloudflare

This needs to be written up but here's quick guide.

https://fossengineer.com/selfhosting-cloudflared-tunnel-docker/

Setting up your domain on Cloudflare

There are a couple of options.

  1. Change your name servers at your domain registrar. This is the easiest if you already have a domain. Cloudflare will import your DNS records via a scan, and you can update any that were missed

  2. Transfer your domain to Cloudflare. This isn't required, but also works.

  3. Register a new domain. If you want a specific domain for your rcon, .com's are cheap. Just register a new one and you'll be ready to point the domain to your CRCON. This also works if you have multiple servers, you can still use sub-domains and keep your main domain clean of DNS records.