Cloudflared-windows-amd64.exe [ FULL ]

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 |

Open or PowerShell and navigate to where cloudflared.exe lives, then run: cloudflared-windows-amd64.exe

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\ : net start cloudflared Or use the Services GUI ( services

cloudflared.exe tunnel login A browser window will open. Log in to your Cloudflare account and select the domain you want to use. This generates a cert.pem file in %USERPROFILE%\.cloudflared\ . That certificate is your global API credential—keep it safe. Tunnels are persistent connections with their own configuration. Let’s create one. Create a configuration file config