-
-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation Issue: Dns-Over-HTTPs with Cloudflared #175
Comments
Hi @iUnknwn , please feel free to submit any changes to the documentation as a Pull request on this repository. The team can look over your suggested changes as part of the entire document, then. |
I was actually looking at this myself, and it seems cloudflared has a service command https://developers.cloudflare.com/argo-tunnel/reference/arguments/#service-command So, it could be possible that the whole manual thing could be simplified nowadays. |
I submitted a small pull request that expands the docs, so a user can setup automatic updating of the cloudflared daemon. It looks like someone already updated the docs with the corrected systemd path. |
In raising this issue, I confirm the following:
{please fill the checkboxes, e.g: [X]}
How familiar are you with the the source code relevant to this issue?:
N/A - Documentation Issue
Expected behaviour:
Documentation on Encrypted DNS via Cloudflared should use correct systemd paths, and provide update instructions.
Actual behaviour:
Documentation instructs users to update the system built-in unit store, instead of the user config store. No update instructions provided.
Steps to reproduce:
N/A - however, issues can be fixed by replacing the systemd unit
/lib/systemd/system
path with/etc/systemd/system/
, which is the user-created store for systemd files.Also, while this is slightly more of a documentation change request, there's no information on updating the cloudflared daemon. While not exactly elegant, something like this could be called as a cron job:
Debug token provided by uploading
pihole -d
log:N/A
Troubleshooting undertaken, and/or other relevant information:
N/A
The text was updated successfully, but these errors were encountered: