starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Bug] New Config.yaml ACL section does not work - Must use old acl_policy_path #762

New Issue
Closed
opened 2025-12-29 02:23:32 +01:00 by adam · 4 comments
adam commented 2025-12-29 02:23:32 +01:00
Owner
Copy Link

Originally created by @W1BTR on GitHub (Aug 12, 2024).

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

On the beta and alphas, the new config structure for enabling acls looks like this:

## Policy
# headscale supports Tailscale's ACL policies.
# Please have a look to their KB to better
# understand the concepts: https://tailscale.com/kb/1018/acls/
policy:
  # The mode can be "file" or "database" that defines
  # where the ACL policies are stored and read from.
  mode: file
  # If the mode is set to "file", the
  # path to a file containing ACL policies.
  # The file can be in YAML or HuJSON format.
  path: "/etc/headscale/acls.json"

However, this does not do anything. Instead, one must use the old config line: acl_policy_path: "" somewhere in the config (I put mine right under).

Expected Behavior

the ACL file is applied

Steps To Reproduce

  1. Create and enable an ACL file
  2. Nothing happens in the logs.

Environment

- OS:Ubuntu 24.04
- Headscale version: 0.23.0-alpha-12 and 0.23.0-beta1

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

No response

Originally created by @W1BTR on GitHub (Aug 12, 2024). ### Is this a support request? - [X] This is not a support request ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior On the beta and alphas, the new config structure for enabling acls looks like this: ``` ## Policy # headscale supports Tailscale's ACL policies. # Please have a look to their KB to better # understand the concepts: https://tailscale.com/kb/1018/acls/ policy: # The mode can be "file" or "database" that defines # where the ACL policies are stored and read from. mode: file # If the mode is set to "file", the # path to a file containing ACL policies. # The file can be in YAML or HuJSON format. path: "/etc/headscale/acls.json" ``` However, this does not do anything. Instead, one must use the old config line: `acl_policy_path: ""` somewhere in the config (I put mine right under). ### Expected Behavior the ACL file is applied ### Steps To Reproduce 1. Create and enable an ACL file 2. Nothing happens in the logs. ### Environment ```markdown - OS:Ubuntu 24.04 - Headscale version: 0.23.0-alpha-12 and 0.23.0-beta1 ``` ### Runtime environment - [X] Headscale is behind a (reverse) proxy - [X] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:23:32 +01:00
adam closed this issue 2025-12-29 02:23:32 +01:00
adam commented 2025-12-29 02:23:32 +01:00
Author
Owner
Copy Link

@hrtkpf commented on GitHub (Aug 13, 2024):

Duplicate of #2024

@hrtkpf commented on GitHub (Aug 13, 2024): Duplicate of #2024
adam commented 2025-12-29 02:23:32 +01:00
Author
Owner
Copy Link

@W1BTR commented on GitHub (Aug 13, 2024):

Duplicate of #2024

Thanks. Searched but couldnt find it.

@W1BTR commented on GitHub (Aug 13, 2024): > Duplicate of #2024 Thanks. Searched but couldnt find it.
adam commented 2025-12-29 02:23:32 +01:00
Author
Owner
Copy Link

@SuperSandro2000 commented on GitHub (Aug 16, 2024):

Could you close the issue if it is indeed duplicated?

@SuperSandro2000 commented on GitHub (Aug 16, 2024): Could you close the issue if it is indeed duplicated?
adam commented 2025-12-29 02:23:32 +01:00
Author
Owner
Copy Link

@W1BTR commented on GitHub (Aug 19, 2024):

Thanks for closing it kradalby, only just seeing this update.

@W1BTR commented on GitHub (Aug 19, 2024): Thanks for closing it kradalby, only just seeing this update.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#762
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?