From 3269cfdca0edd17d3a0e3db4a39dde6deda139d1 Mon Sep 17 00:00:00 2001 From: Florian Preinstorfer Date: Mon, 16 Dec 2024 16:21:29 +0100 Subject: [PATCH] Mention reload and SIGHUP when editing the ACL policy file Fixes: #2284 --- docs/ref/acls.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/ref/acls.md b/docs/ref/acls.md index d7ceb629..fef37a3e 100644 --- a/docs/ref/acls.md +++ b/docs/ref/acls.md @@ -52,7 +52,13 @@ tags to a server they can register, the check of the tags is done on headscale server and only valid tags are applied. A tag is valid if the user that is registering it is allowed to do it. -To use ACLs in headscale, you must edit your `config.yaml` file. In there you will find a `policy.path` parameter. This will need to point to your ACL file. More info on how these policies are written can be found [here](https://tailscale.com/kb/1018/acls/). +To use ACLs in headscale, you must edit your `config.yaml` file. In there you will find a `policy.path` parameter. This +will need to point to your ACL file. More info on how these policies are written can be found +[here](https://tailscale.com/kb/1018/acls/). + +Please reload or restart Headscale after updating the ACL file. Headscale may be reloaded either via its systemd service +(`sudo systemctl reload headscale`) or by sending a SIGHUP signal (`sudo kill -HUP $(pidof headscale)`) to the main +process. Headscale logs the result of ACL policy processing after each reload. Here are the ACL's to implement the same permissions as above: