cloudflared
cloudflared copied to clipboard
Cloudflare Tunnel client (formerly Argo Tunnel)
**Describe the bug** On the documents page https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/installation it lists an option to `Updating with multiple cloudflared instances` with the following instructions > If you are not using Cloudflare’s Load...
We noticed starting with 2023.2.2 or higher, when run as a windows service, the service will not restart. Cloudflared.exe must be killed using task manager to restart the service.
Can the local IP address be used instead.
I see that the binaries link are https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64 But what's the extension of this file? How can I install it on alpine linux? ``` docker run -it alpine apk add...
**Describe the bug** After following the setup instructions ["Advanced setup: Differing usernames"](https://developers.cloudflare.com/cloudflare-one/identity/users/short-lived-certificates/#2-ensure-unix-usernames-match-user-sso-identities), I can only log into my server as the user corresponding to the email address prefix used for...
**Describe the bug** (maybe i should ask this in termux...) I use cloudflared on Termux, Android 12 when i run `./cloudflare tunnel --url ...`, it logs ``` ❯ ./cloudflared tunnel...
2023-02-07T13:22:32Z INF Starting tunnel tunnelID=89aa7e03-18e6-4d43-b670-139495718f06 2023-02-07T13:22:32Z INF Version 2023.2.1 2023-02-07T13:22:32Z INF GOOS: linux, GOVersion: go1.19.3, GoArch: amd64 2023-02-07T13:22:32Z INF Settings: map[cred-file:/root/.cloudflared/89aa7e03-18e6-4d43-b670-139495718f06.json credentials-file:/root/.cloudflared/89aa7e03-18e6-4d43-b670-139495718f06.json p:http2 protocol:http2] 2023-02-07T13:22:32Z INF cloudflared will not automatically...
**Describe the bug** With more then 1 tunnel on this specific machine (Personal, and a tunnel I don't manage) Both tunnels shut down randomly. **To Reproduce** Steps to reproduce the...
**Describe the feature you'd like** Currently the ingress rules only allow matching traffic by hostname, i.e. ```yaml # ... ingress: - hostname: subdomain.domain.com service: https://subdomain.domain.com:9120 - service: http_status:404 ``` I...
I have two domains, one is `a.com` another is `b.com`. I want to create a dns route for `test.a.com`, but it it will instead create a route for `test.a.com.b.com`. Here's...