Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Ability to define a "scheduled renewal blackout" #675

Open
nmarie276 opened this issue May 21, 2024 · 2 comments
Open

Feature request: Ability to define a "scheduled renewal blackout" #675

nmarie276 opened this issue May 21, 2024 · 2 comments

Comments

@nmarie276
Copy link

Hello.

We're using CertifyTheWeb (licensesd version) on our IIS server and, when it's time to renew the certificate, this triggers a IIS website restart. Even if this behaviour is expected, this causes us a downtime to our customers. Currently, as a workaround, we created a Windows scheduled task that:

  • Stops the certifytheweb service at 6:00 AM.
    • Let it as stopped during the working hours.
  • Starts the certifytheweb service at 8:00 PM.
    • The service triggers the certificates renewals if needed.
      Ideally, we would like to control this directly from the CertifyTheWeb UI, by being able to define a "renewal blackout" schedule. As a result, the renewals will be triggered only during the night.

Thanks for your answer.
Regards.

@webprofusion-chrisc
Copy link
Contributor

It's something to consider, but I would recommend you look at using the windows Centralized Certificate Store (CCS) option for your website bindings. This reads the certificate files directly from disk instead of updating the bindings in IIS (which currently triggers a no-operation update to applicationhost.config, which will then cause app pools to recycle).

@nmarie276
Copy link
Author

@webprofusion-chrisc, thanks for this tip. I will study this way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants