Jump to content

Talk:Cloudflared

From ArchWiki
Latest comment: 31 May by 1int3rn in topic Revamp

Out of date?

Most of the instructions on this page no longer seem relevant to the current version (2023.6.1) of `cloudflared` in either the `Extra` repo or in AUR as `cloudflared-bin`. My take is that we should probably rewrite this page to keep it inline with the current version's capabilities.

Specifically, using `cloudflared` for DoH via `proxy-dns` doesn't seem to use the `config.yml` file at all anymore -- the config file only seems to be used for setting up a tunnel for their ZeroTrust offering.

The `Extra` repo version of the program doesn't include a systemd service file either -- the AUR version does though. Creating a service to setup the proxy-dns has become cryptic (as has the help for the program in general) but there are instructions buried in the cloudflare help (links below).

For proxy-dns, everything needs to be done on the commandline when invoking `cloudflared`.

Relevant links for reference:

Aside: I'm thinking there should be two main sections for this wiki page to cover the two primary use cases for the command -- one for DoH/proxy-dns, and one for ZeroTrust tunnels.

Thoughts? Vic acid (talk) 01:33, 25 June 2023 (UTC)Reply

Feel free to use Template:Out of date to mark the obsolete parts of the page. — Lahwaacz (talk) 06:18, 25 June 2023 (UTC)Reply
Why the wiki says "Pending resolution of FS#75999, start and enable cloudflared.service." if no service file is provided? And what is the AUR package that provides the service file? Can we advertise it in the wiki? I will poke the bug issue Fhy (talk) 01:21, 23 January 2024 (UTC)Reply
I updated the entry Fhy (talk) 02:04, 23 January 2024 (UTC)Reply

Revamp

As noted in the warning at the top, the developer has removed the functionality currently described in the text.

I want to remove the outdated sections (3 Checking, 4 Endpoint) and replace the content of the 2 Usage section with:

- quick tunnels: how to quickly expose a local web service for development without requiring a cloudflare account.

- named tunnels: a brief mention of other potentially useful cases that require an account and managed domain name, such as exposing ssh, rdp or tcp.

Does this sound like the right direction for the article? Please let me know if you have any suggestions or objections. 1int3rn (talk) 14:24, 31 May 2026 (UTC)Reply