Renewals and alerts

Nothing to click. Once a day NeverLapse renews what's due and installs it everywhere it's used.

When certificates renew

• Once a day, at 2:00 AM server time by default, the NeverLapse service checks every certificate.
• Anything within 30 days of expiry (or never issued) is renewed.
• Each renewed certificate is installed on every host that uses it right away: imported into Windows, IIS rebound (push hosts: NeverLapse on Windows), files written for Linux, or collected by agents at their next check-in (every minute by default).
• A failed renewal is tried again at the next daily check, for as long as the certificate is inside the renewal window.

Change the time or the number of days under Settings > Renewal. Most people never need to.

Do it now

• Check renewals (Dashboard) runs the daily check right now: renews anything due and deploys it.
• Deploy all now (Dashboard) installs every certificate on every host again, whether it renewed or not. Use it after changing a host's settings (a new IIS binding, a new folder) when you don't want to wait.

Alerts

NeverLapse emails only when something needs you. Set up two things:

1. Settings > Email (SMTP): your mail server. Use Send Test Email to Myself to check it. See Email settings.
2. Settings > Certificate Issuance Notifications: the address that gets alerts (a shared mailbox or a ticketing system's address works well).

You're emailed when:

• an Issue now attempt fails (problems that need a fix stop at once; slow DNS is retried for about 15 minutes);
• the nightly check can't renew a certificate that's due;
• a certificate renewed but couldn't be installed on one or more hosts (the email says which hosts and why);
• a Manual DNS certificate needs new TXT records to renew.

Want to hear about successful renewals too? Tick Also email this address when a certificate is issued or renewed on the same settings page: useful when the certificate also lives somewhere NeverLapse doesn't update, like a firewall.

The Dashboard at a glance

• Healthy: valid for a while yet.
• Expiring soon: close to expiry. Normal right before a renewal; worth a look if it stays.
• Needs fixing: a failed issue, renewal or deployment.