docs
docs copied to clipboard
Documentation Issue: Dns-Over-HTTPs with Cloudflared
In raising this issue, I confirm the following: {please fill the checkboxes, e.g: [X]}
- [X] I have read and understood the contributors guide.
- [X] The issue I am reporting can be replicated.
- [X] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).
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:
echo "Updating Cloudflared Daemon..."
wget -P /tmp https://bin.equinox.io/c/VdrWdbjqyF/cloudflared-stable-linux-arm.tgz
systemctl stop cloudflared
tar -C /opt/cloudflared -xzf /tmp/cloudflared-stable-linux-arm.tgz
systemctl start cloudflared
rm /tmp/cloudflared-stable-linux-arm.tgz
echo "Cloudflared update complete."
Debug token provided by uploading pihole -d
log:
N/A
Troubleshooting undertaken, and/or other relevant information:
N/A
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.
https://github.com/pi-hole/docs
Also note that this is a community-provided guide initially written by @bendews (https://github.com/pi-hole/docs/pull/23) and later updated/extended by others. They might want to comment on this as well.
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.
I was actually looking at this myself, and it seems cloudflared has a service command
@dschaper yeah I have this in #186