tls-acme

Compare ACME challenge types and validate certificate issuance against staging endpoints.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/MysticRyuujin/spirens --skill tls-acme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tls-acme
Source: https://github.com/MysticRyuujin/spirens/tree/main/tls-acme
Command: npx skills add https://github.com/MysticRyuujin/spirens --skill tls-acme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ACME protocols simplify automated certificate issuance by selecting the appropriate challenge type (DNS-01, HTTP-01, TLS-ALPN-01) and guiding secure TLS setup for new hostnames and wildcards, while highlighting rate limits and staging endpoints.

Core Features & Use Cases

  • ACME challenge guidance: compare DNS-01, HTTP-01, and TLS-ALPN-01 to match reachability, wildcard needs, and deployment constraints.
  • Risk and limit awareness: explain rate limits, staging usage, and validation pitfalls to avoid renewal issues.
  • Operational workflows: outline steps to move from test issuance to production in a Traefik-based or similar environment.

Quick Start

Begin by using the staging ACME endpoint to issue a test certificate with DNS-01 for a sample wildcard hostname and observe the validation flow.

Frequently Asked Questions about tls-acme

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right ACME challenge type for TLS certificate issuance?

ACME challenges differ by validation method: DNS-01 verifies wildcard domains via TXT records, HTTP-01 validates public web servers over port 80, and TLS-ALPN-01 validates over port 443, making each suited to different reachability and deployment constraints.

When do I need to use the DNS-01 challenge instead of HTTP-01?

You need DNS-01 instead of HTTP-01 when issuing wildcard certificates or when validating hostnames on private networks like LAN or VPN, where public HTTP endpoints are unreachable by the ACME CA for verification.

How do I test ACME certificate issuance without hitting production rate limits?

Test ACME certificate issuance safely by using the staging ACME endpoint. This allows you to validate the challenge flow and observe issuance behavior for new hostnames without encountering strict production rate limits.

Does the TLS-ALPN-01 challenge work for wildcard certificates across a VPN?

TLS-ALPN-01 does not support wildcard certificates; it validates single hostnames over port 443. For wildcard certificates across a VPN or LAN, you must use the DNS-01 challenge instead.

What are the limitations of using HTTP-01 for ACME certificate validation?

HTTP-01 limitations include requiring port 80 to be publicly reachable and an inability to issue wildcard certificates. It is unsuitable for internal LAN or VPN hostnames where the CA cannot reach the HTTP endpoint.

How do I automate Traefik TLS setup with ACME challenges for new hostnames?

Automate Traefik TLS setup by configuring the ACME challenge type matching your network reachability, testing issuance against staging endpoints, and then moving the validated workflow to production for new hostnames.