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] tailscale cert #793

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

Originally created by @Integral-Tech on GitHub (Sep 16, 2024).

Use case

The Official Tailscale documentaion introduces how to enable HTTPS and use tailscale cert to obtain an SSL certificate. However, it seems that this feature hasn't been supported by Headscale.

Description

Add tailscale cert feature for Headscale

Contribution

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

How can it be implemented?

No response

Originally created by @Integral-Tech on GitHub (Sep 16, 2024). ### Use case [The Official Tailscale documentaion](https://tailscale.com/kb/1153/enabling-https) introduces how to enable HTTPS and use ```tailscale cert``` to obtain an SSL certificate. However, it seems that this feature hasn't been supported by Headscale. ### Description Add ```tailscale cert``` feature for Headscale ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? _No response_
adam added the enhancementno-stale-bot labels 2025-12-29 02:24:06 +01:00
adam commented 2025-12-29 02:24:06 +01:00
Author
Owner
Copy Link

@Permanently commented on GitHub (Oct 10, 2024):

I wish I found this submission before spending the last couple of hours hacking at the TLS settings in an attempt to get that command working. I was under the assumption the TLS configuration was for this command, and that me reverse-proxying Headscale through NGINX was messing it up. :|

Edit: also just realised this is a duplicate of #1921

@Permanently commented on GitHub (Oct 10, 2024): I wish I found this submission before spending the last couple of hours hacking at the TLS settings in an attempt to get that command working. I was under the assumption the TLS configuration was for this command, and that me reverse-proxying Headscale through NGINX was messing it up. :| **Edit:** also just realised this is a duplicate of #1921
adam commented 2025-12-29 02:24:06 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 9, 2025):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Jan 9, 2025): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:24:07 +01:00
Author
Owner
Copy Link

@pwall2222 commented on GitHub (Apr 11, 2025):

It would be needed to implement the /machine/set-dns to set the TXT record required for the ACME (LetsEncrypt) challenge.

@pwall2222 commented on GitHub (Apr 11, 2025): It would be needed to implement the [`/machine/set-dns`](https://github.com/tailscale/tailscale/blob/11d1dd2aed2a34e151bfd598d4944f778c7af149/control/controlclient/direct.go#L1504) to set the `TXT` record required for the ACME (LetsEncrypt) challenge.
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 no-stale-bot
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#793
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?