Wildcard cert setup missing _acme-validation step in flyctl instructions

TL;DR

A maintainer acknowledged it the same day and the fix went out in the 145 release.

Steps

1. I was setting up a wildcard certificate on Fly and the CLI never told me I needed an _acme-validation DNS entry, so the cert couldnt be issued. The output only mentioned the A record for directing traffic, which is a separate thing from validation. A maintainer acknowledged it the same day and the fix went out in the 145 release. Closed October 2020.
2. What actually fixes it (verified in the thread):
3. Wildcard certs need a DNS-01 challenge, which means an acme-validation TXT record, but flyctl was only showing the traffic-pointing instructions and skipping the validation step entirely. The fix was in the flyctl 145 release, which added the missing instructions to the certs output. If your wildcard cert is stuck unissued, check you created the acme-validation record, thats the step the old output omitted.

When to use

You are seeing this: The situation: I was setting up a wildcard certificate on Fly and the CLI never told me I needed an acme-validation DNS entry, so the cert couldnt be issued. Use this skill when you run into "Wildcard cert setup missing acme-validation step in flyctl instructions".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Someone asked: I was setting up a wildcard certificate on Fly and the CLI never told me I needed an acme-validation DNS entry, so the cert couldnt be issued. The output only mentioned the A record for directing traffic, which is a separate thing from validation. A maintainer acknowledged it the same day and the fix went out in the 145 release. Closed October 2020. The verified answer: Wildcard certs need a DNS-01 challenge, which means an acme-validation TXT record, but flyctl was only showing the traffic-pointing instructions and skipping the validation step entirely. The fix was in the flyctl 145 release, which added the missing instructions to the certs output. If your wildcard cert is stuck unissued, check you created the acme-validation record, thats the step the old output omitted. Full thread: https://vectle.com/threads/thru3WwF9RmXQ9HGory_UkurQ