BREAKING: Fly.io MINOR 🟡 Certificate issuance delays [vvsn69zvhbps]

Fly.io experiencing certificate issuance delays. Partial disruption affecting new deployments and renewals. Immediate workarounds and monitoring steps inside.

BREAKING: Fly.io Certificate Issuance Delays – What You Need to Know

Status: Investigating | Severity: Minor | Impact: Partial | Updated: Now

---

What's Affected

Fly.io is currently experiencing delays in SSL/TLS certificate issuance and renewal. This impacts:

New app deployments requiring fresh certificates

Certificate renewals for existing apps (typically 30 days before expiration)

Custom domain additions with auto-HTTPS enabled

Apps transitioning between regions

Who's hit hardest: Developers deploying new projects or scaling infrastructure today. Existing running apps with valid certificates are unaffected.

---

Immediate Workarounds (Do This Now)

1. Delay Non-Critical Deployments

If your deployment isn't urgent, wait 2-4 hours for the issue to resolve. Fly.io typically resolves certificate issues quickly.

2. Extend Certificate Validity Manually

If you're near renewal: ```bash flyctl certs check <your-domain> ``` This forces a manual check. If it fails, contact Fly.io support with your app name—they can manually trigger renewal.

3. Use Cloudflare as Temporary Shield

Point your DNS to Cloudflare (free tier works)

Enable "Full" SSL mode in Cloudflare

Cloudflare will proxy traffic while Fly.io resolves certificate issues

Your app stays online to users

4. Deploy to Alternative Region

If available, deploy to a different Fly.io region: ```bash flyctl deploy --region <different-region> ``` Some regions may be unaffected.

5. Temporarily Disable HTTPS Requirement

For development/staging only—not production: ```bash flyctl config validate

Remove auto_start_machines = true if causing issues

```

---

How to Check if You're Affected

1. Check cert status: ```bash flyctl certs list flyctl certs check <your-domain> ```

2. Look for these error patterns: - "Certificate issuance in progress" - "ACME challenge failed" - "Rate limit exceeded" (common with Let's Encrypt)

3. Monitor your app health: ```bash flyctl status ``` If status shows "Degraded" with cert errors, you're impacted.

---

Alternative Hosting (Temporary Pivot)

If you need a solution *today*:

Vercel – Best for Next.js/Node; certs instant

Railway – Docker-friendly; 5-min setup

Render – Static sites + APIs; solid cert handling

DigitalOcean App Platform – Traditional but reliable

Heroku – Slower, but stable certificate handling

None are perfect for long-term cost, but any work for 48-72 hours.

---

Monitor for Recovery

Real-time status:

Check status.fly.io every 30 minutes

Monitor the #incidents channel in Fly.io Discord

Watch your app logs: flyctl logs

What recovery looks like:

Certs begin issuing within minutes

No redeployment needed—automatic renewal kicks in

Existing connections stay stable

Estimated resolution: 2-6 hours based on historical Fly.io incident patterns.

---

The Bottom Line

This is not a data breach or infrastructure failure—it's a certificate automation hiccup. Your apps stay online if they already have valid certs. New deployments will queue briefly, then process normally.

Don't panic. Don't migrate. Wait it out or use Cloudflare as a buffer.

We'll update this post as Fly.io provides status changes. Stay sharp.