Cloudflared-windows-amd64.exe Info

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.exe tunnel run my-first-tunnel Your local service is now live at https://myapp.yourdomain.com . For persistent operation (reboots, logoffs), install Cloudflared as a Windows service. cloudflared-windows-amd64.exe

If you run a web server on your Windows machine—whether for development, home automation, or a personal website—you know that exposing it to the internet can be risky. Port forwarding is messy, dynamic DNS is a hassle, and your ISP might block incoming traffic altogether. net start cloudflared Or use the Services GUI ( services

– Check logs: cloudflared.exe tunnel run --config C:\path\to\config.yml my-first-tunnel (run manually first). – Check logs: cloudflared

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

Invoke-WebRequest -Uri "https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-windows-amd64.exe" -OutFile "$env:USERPROFILE\Downloads\cloudflared.exe" Move it to a permanent location, e.g., C:\cloudflared\cloudflared.exe , and add that folder to your PATH for easy access. Cloudflared needs to authenticate with your Cloudflare account.