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

failed to read or create private key #583

New Issue
Closed
opened 2025-12-29 02:20:49 +01:00 by adam · 11 comments
adam commented 2025-12-29 02:20:49 +01:00
Owner
Copy Link

Originally created by @chowkai on GitHub (Nov 29, 2023).

server start fail
2023-11-29T16:52:35+08:00 TRC DNS configuration loaded dns_config={"ExitNodeFilteredSet":null,"FallbackResolvers":[{"Addr":"1.1.1.1"}],"Nameservers":["1.1.1.1"]}
2023-11-29T16:52:36+08:00 INF No private key file at path, creating... path=
2023-11-29T16:52:36+08:00 FTL ../../../home/runner/work/headscale/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory"

but my config file have
# Listens over UDP at the configured address for STUN connections - to help with NAT traversal.
# When the embedded DERP server is enabled stun_listen_addr MUST be defined.
#
# For more details on how this works, check this great article: https://tailscale.com/blog/how-tailscale-works/
stun_listen_addr: "0.0.0.0:3478"

# Private key used to encrypt the traffic between headscale DERP
# and Tailscale clients.
# The private key file will be autogenerated if it's missing.
#
private_key_path: /var/lib/headscale/derp_server_private.key
Originally created by @chowkai on GitHub (Nov 29, 2023). server start fail 2023-11-29T16:52:35+08:00 TRC DNS configuration loaded dns_config={"ExitNodeFilteredSet":null,"FallbackResolvers":[{"Addr":"1.1.1.1"}],"Nameservers":["1.1.1.1"]} 2023-11-29T16:52:36+08:00 INF No private key file at path, creating... path= 2023-11-29T16:52:36+08:00 FTL ../../../home/runner/work/headscale/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory" but my config file have # Listens over UDP at the configured address for STUN connections - to help with NAT traversal. # When the embedded DERP server is enabled stun_listen_addr MUST be defined. # # For more details on how this works, check this great article: https://tailscale.com/blog/how-tailscale-works/ stun_listen_addr: "0.0.0.0:3478" # Private key used to encrypt the traffic between headscale DERP # and Tailscale clients. # The private key file will be autogenerated if it's missing. # private_key_path: /var/lib/headscale/derp_server_private.key
adam added the bug label 2025-12-29 02:20:49 +01:00
adam closed this issue 2025-12-29 02:20:49 +01:00
adam commented 2025-12-29 02:20:50 +01:00
Author
Owner
Copy Link

@sp391607254 commented on GitHub (Nov 29, 2023):

when i use docker compose up -d

2023-11-29T20:10:17+08:00 TRC DNS configuration loaded dns_config={"ExitNodeFilteredSet":null,"Nameservers":["192.168.10.10"],"Proxied":true,"Resolvers":[{"Addr":"192.168.10.10"}]}
2023-11-29T20:10:18+08:00 INF No private key file at path, creating... path=
2023-11-29T20:10:18+08:00 FTL go/src/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory"

@sp391607254 commented on GitHub (Nov 29, 2023): when i use docker compose up -d 2023-11-29T20:10:17+08:00 TRC DNS configuration loaded dns_config={"ExitNodeFilteredSet":null,"Nameservers":["192.168.10.10"],"Proxied":true,"Resolvers":[{"Addr":"192.168.10.10"}]} 2023-11-29T20:10:18+08:00 INF No private key file at path, creating... path= 2023-11-29T20:10:18+08:00 FTL go/src/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory"
adam commented 2025-12-29 02:20:50 +01:00
Author
Owner
Copy Link

@hugoduraes commented on GitHub (Nov 29, 2023):

The config example file is missing the private_key_path. It was removed on this commit.

@hugoduraes commented on GitHub (Nov 29, 2023): The [config example](https://github.com/juanfont/headscale/blob/main/config-example.yaml) file is missing the `private_key_path`. It was removed on this [commit](https://github.com/juanfont/headscale/commit/a59aab20811cc42c7501ea9aab88a12c2ba5d47e#diff-0997963b54113de6bb19667e1ad7c561a2e6cbba874d4fe671c3e116252f3d25L47).
adam commented 2025-12-29 02:20:50 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Nov 30, 2023):

Please use the git tag equal to the release you are using when browsing documentation and examples.

@kradalby commented on GitHub (Nov 30, 2023): Please use the git tag equal to the release you are using when browsing documentation and examples.
adam commented 2025-12-29 02:20:50 +01:00
Author
Owner
Copy Link

@myaklez commented on GitHub (Jan 25, 2024):

I had the same error, when trying to start the service it sent me the error that it could not create the key or that the directory did not exist. All tests I am doing are on an OS: Rocky Linux 8.9 (Green Obsidian) x86_64
Kernel: 4.18.0-513.11.1.el8_9.x86_64.
At first I thought it was SElinux that was blocking me, but after analyzing the logs, I realized that it was not the cause of my headache, I was analyzing the configuration file and everything was fine, there was no error syntax, and I followed all the possible solutions referred to and none of them worked for me. I still had the message:

FTL ../../../home/runner/work/headscale/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory".

So as a final task, I set out to change the version of headscale from 0.22.3 to v0.23.0-alpha3, once the change was made, I finally have Headscale running.

Captura de Pantalla 2024-01-25 a la(s) 10 21 04

@myaklez commented on GitHub (Jan 25, 2024): I had the same error, when trying to start the service it sent me the error that it could not create the key or that the directory did not exist. All tests I am doing are on an OS: Rocky Linux 8.9 (Green Obsidian) x86_64 Kernel: 4.18.0-513.11.1.el8_9.x86_64. At first I thought it was SElinux that was blocking me, but after analyzing the logs, I realized that it was not the cause of my headache, I was analyzing the configuration file and everything was fine, there was no error syntax, and I followed all the possible solutions referred to and none of them worked for me. I still had the message: **FTL ../../../home/runner/work/headscale/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory".** So as a final task, I set out to change the version of headscale from 0.22.3 to v0.23.0-alpha3, once the change was made, I finally have Headscale running. ![Captura de Pantalla 2024-01-25 a la(s) 10 21 04](https://github.com/juanfont/headscale/assets/84055031/326ce0a3-4bba-4ff2-aff0-8d110b7427dd)
adam commented 2025-12-29 02:20:50 +01:00
Author
Owner
Copy Link

@qNFCp commented on GitHub (Apr 29, 2024):

Same error, after changing from 0.22.3 to 0.23.0-alpha9, Headscale run successfully.

@qNFCp commented on GitHub (Apr 29, 2024): Same error, after changing from 0.22.3 to 0.23.0-alpha9, Headscale run successfully.
adam commented 2025-12-29 02:20:51 +01:00
Author
Owner
Copy Link

@n0valis commented on GitHub (May 13, 2024):

I have the same error but would like to stay on 0.22.3
What can I do?

my config.yaml contains the path:
private_key_path: /var/lib/headscale/noise_private.key

error messsage:
`2024-05-13T00:23:51+02:00 WRN 'ip_prefixes' not configured, falling back to default: [100.64.0.0/10]
2024-05-13T00:23:51+02:00 INF No private key file at path, creating... path=

2024-05-13T00:23:51+02:00 FTL ../home/runner/work/headscale/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory"`

@n0valis commented on GitHub (May 13, 2024): I have the same error but would like to stay on 0.22.3 What can I do? my config.yaml contains the path: private_key_path: /var/lib/headscale/noise_private.key error messsage: `2024-05-13T00:23:51+02:00 WRN 'ip_prefixes' not configured, falling back to default: [100.64.0.0/10] 2024-05-13T00:23:51+02:00 INF No private key file at path, creating... path= 2024-05-13T00:23:51+02:00 FTL ../home/runner/work/headscale/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory"`
adam commented 2025-12-29 02:20:51 +01:00
Author
Owner
Copy Link

@myaklez commented on GitHub (May 13, 2024):

Your ideas are to stay in the official version without going up to the
alpha version, that's how it is. If so, I would like to know what
version of the operating system you are using, this way only the
committees that were corrected from the alpha version would be added.

El dom, 12 may 2024 a las 16:21, n0valis @.***>)
escribió:

I have the same error but would like to stay on 0.22.3
What can I do?

—
Reply to this email directly, view it on GitHub
https://github.com/juanfont/headscale/issues/1624#issuecomment-2106393095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUBJH5YKGJIUOQ4DXOVKPWTZB7TPPAVCNFSM6AAAAAA77C36JWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGM4TGMBZGU
.
You are receiving this because you commented.Message ID:
@.***>

--
Ricardo Alexander Lopez Medina

  GNU/Linux 1999-2021

Redhat, CentOS, CL, Fedora,OpenSuse,FreeBSD,RockyLinux,AlmaLinux

@myaklez commented on GitHub (May 13, 2024): Your ideas are to stay in the official version without going up to the alpha version, that's how it is. If so, I would like to know what version of the operating system you are using, this way only the committees that were corrected from the alpha version would be added. El dom, 12 may 2024 a las 16:21, n0valis ***@***.***>) escribió: > I have the same error but would like to stay on 0.22.3 > What can I do? > > — > Reply to this email directly, view it on GitHub > <https://github.com/juanfont/headscale/issues/1624#issuecomment-2106393095>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AUBJH5YKGJIUOQ4DXOVKPWTZB7TPPAVCNFSM6AAAAAA77C36JWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGM4TGMBZGU> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- Ricardo Alexander Lopez Medina GNU/Linux 1999-2021 Redhat, CentOS, CL, Fedora,OpenSuse,FreeBSD,RockyLinux,AlmaLinux
adam commented 2025-12-29 02:20:51 +01:00
Author
Owner
Copy Link

@n0valis commented on GitHub (May 13, 2024):

Your ideas are to stay in the official version without going up to the alpha version, that's how it is.

I think my fault was to not thouroughly check the config.yaml I forgot to check the changes between versions.
Starting with a fresh config.yaml form 22.3 resolved the issue

@n0valis commented on GitHub (May 13, 2024): > Your ideas are to stay in the official version without going up to the alpha version, that's how it is. I think my fault was to not thouroughly check the config.yaml I forgot to check the changes between versions. Starting with a fresh config.yaml form 22.3 resolved the issue
adam commented 2025-12-29 02:20:51 +01:00
Author
Owner
Copy Link

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

Having this issue with a fresh install and the default example config. Ill be using a reverse proxy and have no path set.

@W1BTR commented on GitHub (Aug 6, 2024): Having this issue with a fresh install and the default example config. Ill be using a reverse proxy and have no path set.
adam commented 2025-12-29 02:20:51 +01:00
Author
Owner
Copy Link

@Xopher00 commented on GitHub (Sep 4, 2024):

I was having this exact same issue after using a modified config-example file. Using build 0.23.0-alpha9 also solved the issue for me :)

@Xopher00 commented on GitHub (Sep 4, 2024): I was having this exact same issue after using a modified config-example file. Using build 0.23.0-alpha9 also solved the issue for me :)
adam commented 2025-12-29 02:20:52 +01:00
Author
Owner
Copy Link

@W1BTR commented on GitHub (Sep 6, 2024):

Looks like thats the issue @Xopher00 - ty.

@W1BTR commented on GitHub (Sep 6, 2024): Looks like thats the issue @Xopher00 - ty.
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#583
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?