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

Add DNS01 Challenge #240

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

Originally created by @philippderdiedas on GitHub (Mar 16, 2022).

Feature request

Implement ACME-DNS01 Challenge

Makes it possible to use wildcard certificates or when http challenge is not an option.

Could be achieved by using lego

Originally created by @philippderdiedas on GitHub (Mar 16, 2022). **Feature request** Implement ACME-DNS01 Challenge Makes it possible to use wildcard certificates or when http challenge is not an option. Could be achieved by using [lego](https://github.com/go-acme/lego)
adam added the enhancementstale labels 2025-12-29 01:24:41 +01:00
adam closed this issue 2025-12-29 01:24:41 +01:00
adam commented 2025-12-29 01:24:42 +01:00
Author
Owner
Copy Link

@renne commented on GitHub (Aug 13, 2023):

We're running Headscale + Tailscale as an ingress router with ports 80 and 443 forwarded to a web-server on the same host.
There is no way to use ports 80 and 443 for the Let's Encrypt http challenge.

Please add the ACME-DNS01 challenge via LEGO.

@renne commented on GitHub (Aug 13, 2023): We're running Headscale + Tailscale as an ingress router with ports 80 and 443 forwarded to a web-server on the same host. There is no way to use ports 80 and 443 for the Let's Encrypt http challenge. Please add the ACME-DNS01 challenge via [LEGO](https://github.com/go-acme/lego).
adam commented 2025-12-29 01:24:43 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 10, 2024):

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

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

@github-actions[bot] commented on GitHub (Mar 18, 2024):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Mar 18, 2024): This issue was closed because it has been inactive for 14 days since being marked as stale.
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 stale
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#240
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?