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

[Feature] Support self-signed TLS (other than Let's Encrypt) #835

New Issue
Closed
opened 2025-12-29 02:24:39 +01:00 by adam · 3 comments
adam commented 2025-12-29 02:24:39 +01:00
Owner
Copy Link

Originally created by @cg31 on GitHub (Oct 18, 2024).

Use case

We can use self-signed TLS service without outside service like Let's Encrypt, for simple network.

Description

Headscale support Let's Encrypt, but it still needs domain name, and it also makes Headscale depending on other service.

Nowadays we can use mkcert or openssl to generate self-signed certificate, they can be done with IP only.

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

  1. User generate local CA with mkcert or openssl
  2. User installs the CA on all nodes
  3. User creates a new certificate with CA for the headscale server
  4. Headscale uses the certificate with ListenAndServeTLS to provide TLS service, client nodes (Tailscale) use the installed CA to verify the certificate.
Originally created by @cg31 on GitHub (Oct 18, 2024). ### Use case We can use self-signed TLS service without outside service like Let's Encrypt, for simple network. ### Description Headscale support Let's Encrypt, but it still needs domain name, and it also makes Headscale depending on other service. Nowadays we can use mkcert or openssl to generate self-signed certificate, they can be done with IP only. ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? 1. User generate local CA with mkcert or openssl 2. User installs the CA on all nodes 3. User creates a new certificate with CA for the headscale server 4. Headscale uses the certificate with ListenAndServeTLS to provide TLS service, client nodes (Tailscale) use the installed CA to verify the certificate.
adam added the enhancement label 2025-12-29 02:24:39 +01:00
adam closed this issue 2025-12-29 02:24:40 +01:00
adam commented 2025-12-29 02:24:40 +01:00
Author
Owner
Copy Link

@hopleus commented on GitHub (Oct 18, 2024):

Isn't that what you're suggesting?

https://headscale.net/ref/tls/#bring-your-own-certificate

@hopleus commented on GitHub (Oct 18, 2024): Isn't that what you're suggesting? https://headscale.net/ref/tls/#bring-your-own-certificate
adam commented 2025-12-29 02:24:40 +01:00
Author
Owner
Copy Link

@cg31 commented on GitHub (Oct 18, 2024):

I tried it with certificate, but it doesn't work, and headscale report error "headscale/cli/utils.go:124 > Could not connect: context deadline exceeded"

When I look inside headscale, it still uses ListenAndServe, ListenAndServeTLS can use paths to cert and key directly.

@cg31 commented on GitHub (Oct 18, 2024): I tried it with certificate, but it doesn't work, and headscale report error "headscale/cli/utils.go:124 > Could not connect: context deadline exceeded" When I look inside headscale, it still uses ListenAndServe, ListenAndServeTLS can use paths to cert and key directly.
adam commented 2025-12-29 02:24:40 +01:00
Author
Owner
Copy Link

@cg31 commented on GitHub (Oct 23, 2024):

Isn't that what you're suggesting?

https://headscale.net/ref/tls/#bring-your-own-certificate

Turns out... it works after trying again, only I need to use 443 as serving port.

But "headscale nodes list" seems not working anymore, but it doesn't matter.

@cg31 commented on GitHub (Oct 23, 2024): > Isn't that what you're suggesting? > > https://headscale.net/ref/tls/#bring-your-own-certificate Turns out... it works after trying again, only I need to use 443 as serving port. But "headscale nodes list" seems not working anymore, but it doesn't matter.
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 enhancement
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#835
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?