Cloudflared-windows-amd64.exe Direct

cloudflared.exe tunnel create my-first-tunnel This creates a tunnel (with a UUID) and stores its credentials in .cloudflared . It also creates a tunnel configuration file template.

For TCP services, you must also set up Cloudflare Access (or use cloudflared access tcp on the client side). For temporary sharing (e.g., a demo), you don’t even need a domain. Run: cloudflared-windows-amd64.exe

net start cloudflared Or use the Services GUI ( services.msc ). The service automatically runs at boot. | Local Service | Example URL | Config service line | |------------------------|--------------------------------------|--------------------------------------| | IIS (default website) | http://localhost:80 | service: http://localhost:80 | | Node.js dev server | http://localhost:3000 | service: http://localhost:3000 | | Jellyfin / Plex | http://localhost:8096 | service: http://localhost:8096 | | SMB / RDP (via Access) | tcp://localhost:3389 | service: tcp://localhost:3389 | | SSH | tcp://localhost:22 | service: tcp://localhost:22 | cloudflared

cloudflared.exe tunnel route dns my-first-tunnel myapp.yourdomain.com This creates a DNS record at Cloudflare pointing to the tunnel. Create a configuration file config.yml in %USERPROFILE%\.cloudflared\ : For temporary sharing (e

First, ensure your config is ready. Then:

– Add cloudflared.exe as an exception in Windows Defender or your third-party AV.