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

config-example.yaml is missing private key path #609

New Issue
Closed
opened 2025-12-29 02:21:09 +01:00 by adam · 2 comments
adam commented 2025-12-29 02:21:09 +01:00
Owner
Copy Link

Originally created by @ghost on GitHub (Jan 6, 2024).

After trying to install headscale for a couple of hours without any success, using native Ubuntu installation as well as docker, running behind a reverse proxy and without it, I found what seems to be a missing line in the official config-example.yaml by chance via another config file provided by some person on Youtube:

# Private key used to encrypt the traffic between headscale
# and Tailscale clients.
# The private key file will be autogenerated if it's missing.
#
private_key_path: /var/lib/headscale/private.key
Originally created by @ghost on GitHub (Jan 6, 2024). After trying to install headscale for a couple of hours without any success, using native Ubuntu installation as well as docker, running behind a reverse proxy and without it, I found what seems to be a missing line in the official config-example.yaml by chance via another config file provided by some person on Youtube: ``` # Private key used to encrypt the traffic between headscale # and Tailscale clients. # The private key file will be autogenerated if it's missing. # private_key_path: /var/lib/headscale/private.key ```
adam added the bug label 2025-12-29 02:21:09 +01:00
adam closed this issue 2025-12-29 02:21:09 +01:00
adam commented 2025-12-29 02:21:10 +01:00
Author
Owner
Copy Link

@masterwishx commented on GitHub (Jan 7, 2024):

you should use config from lasted version

@masterwishx commented on GitHub (Jan 7, 2024): you should use config from lasted version
adam commented 2025-12-29 02:21:10 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Jan 11, 2024):

We mention this in the readme

Note: Always select the same GitHub tag as the released version you use to ensure you have the correct example configuration and documentation. The main branch might contain unreleased changes.

if you are trying to install 0.22.3, you need to select that tag as that private key was removed in main in preparation for 0.23.0

@kradalby commented on GitHub (Jan 11, 2024): We mention this in the readme > Note: Always select the same GitHub tag as the released version you use to ensure you have the correct example configuration and documentation. The main branch might contain unreleased changes. if you are trying to install 0.22.3, you need to select that tag as that private key was removed in main in preparation for 0.23.0
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#609
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?