summaryrefslogtreecommitdiffstats
path: root/docs/manual/automatic-renewal.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/manual/automatic-renewal.md')
-rw-r--r--docs/manual/automatic-renewal.md34
1 files changed, 0 insertions, 34 deletions
diff --git a/docs/manual/automatic-renewal.md b/docs/manual/automatic-renewal.md
deleted file mode 100644
index 16ae606..0000000
--- a/docs/manual/automatic-renewal.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar: manual
----
-
-# Automatic renewal
-
-## Scheduled task
-A single scheduled task is responsible to renew *all* certificates created by the program,
-but will only do so when it's actually neccessary. The task is created by the program itself
-after successfully creating the first certificate. The task runs every day and checks two
-conditions to determine if it should renew:
-- If the certificate is getting too old. This is based on the known history stored in the file.
-- If the target (list of domains) has changed, e.g. an extra binding has been added to an IIS site.
-
-### Customization
-The default renewal period of 55 days can be changed in [settings.json](/win-acme/reference/settings).
-Other properties of the scheduled task can also be changed that way, or from the Task Scheduler itself,
-as long as its name left unmodified. By default it runs at 9:00 am using the `SYSTEM` account.
-
-### Health checks
-The health of the scheduled task is checked each time the program is run manually. It can also
-be (re)created from the menu (`More options...` > `(Re)create scheduled task`).
-
-## Monitoring
-The renewal process can be monitored from the Windows Event Viewer and log files
-written to `%programdata%\win-acme\logs`. You can also set up email notifications
-by configuring a mail server in [settings.json](/win-acme/reference/settings).
-You can test these notifications from the menu (`More options...` > `Test email notification`).
-
-## Testing and troubleshooting
-To test or troubleshoot the renewal process, renewals can be triggered manually from the menu or the
-command line with the `--renew --force` switches. We recommend doing so while running with the
-`--verbose` parameter to get maximum log visibility. When listing the details for a renewal, the
-program will show any errors that have been recorded during previous runs. \ No newline at end of file