docs: clarify common cloudflared service install error#27904
Merged
ranbel merged 2 commits intocloudflare:productionfrom Feb 4, 2026
Merged
docs: clarify common cloudflared service install error#27904ranbel merged 2 commits intocloudflare:productionfrom
ranbel merged 2 commits intocloudflare:productionfrom
Conversation
OTonGitHub
requested review from
a team,
nikitacano and
ranbel
as code owners
ranbel
approved these changes
Feb 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a small clarification to the Linux “run as a service” docs
around installing the
cloudflaredsystemd service withsudo.On most systems the install step needs elevated privileges, which means
$HOMEresolves to/root. When that happens,cloudflaredmay not finda config file created under a user’s home directory unless the config
path is passed explicitly.
This behavior is already tracked in an earlier issue and closed as
not planned. The note just documents the workaround so users don’t get
stuck on this step.
Related issue:
cloudflare/cloudflared#1457
Documentation checklist