You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/installation.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,8 @@ The app runs in Community Edition mode by default, see [Licensing](licensing.md)
31
31
32
32
By default the app will check for updates when you open the UI. If you do not regularly open the UI, it's worth checking for updates periodically. Some updates are critical to ensure continuous operation, and only the latest version is supported.
33
33
34
+
To upgrade manually you can download the latest version and install it. You don't normally need to uninstall first etc.
35
+
34
36
The latest release notes for the app can be found at https://certifytheweb.com/home/changelog
35
37
36
38
### Settings are preserved between installs/upgrades
Copy file name to clipboardExpand all lines: docs/http-validation.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
id: http-validation
3
-
title: HTTP Validation (http-01)
3
+
title: HTTP Domain Validation (http-01)
4
4
---
5
5
## Why use HTTP Validation?
6
6
To request a certificate from Let's Encrypt (or any Certificate Authority), you need to provide some kind of proof that you are entitled to receive the certificate for given domain(s). Let's Encrypt support two methods of validation to prove control of your domain, `http-01` (validation over HTTP) and `dns-01` ([validation via DNS](dns/validation.md)). Wildcard domain certificates (those covering `*.yourdomain.com`) can only be requested using DNS validation.
Copy file name to clipboardExpand all lines: docs/intro.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ id: intro
3
3
title: Getting Started
4
4
---
5
5
6
-
# Introduction
6
+
# Getting Started
7
7
8
8
[Certify The Web](https://certifytheweb.com) - *Certify Certificate Manager* is the most popular UI for professional ACME certificate management on Windows, allowing you to easily request, deploy, auto-renew and manage free SSL/TLS [certificates](guides/certificates.md) from Certificate Authorities such as **[Let's Encrypt, BuyPass Go, Google Trust Services, ZeroSSL and custom CAs](guides/certificate-authorities.md)**.
Copy file name to clipboardExpand all lines: docs/renewals.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,17 +7,24 @@ All certificates have an expiry date, after which they cannot be used to secure
7
7
8
8
**By default, Certify will attempt to auto-renew your certificates and tell you if something goes wrong**
9
9
10
-
The app includes a Certify background service which performs all the main function for managed certificates, so you don't need to leave the UI open for renewals etc to run. If the renewal process fails repeatedly, **it will try to notify you** via our API before certificate expiration becomes a problem, unless you have disabled the *Enable Status Reports to Dashboard* option under Settings. **Ensure that your 'Certificate Authority Account' under Settings > Certificate Authorities is set to a real, monitored, email address** preferably accessible by others if you are a group of site administrators. You do not need to configure anything else like SMTP relays etc. to use this feature, it's all automatic by default.
10
+
The renewal frequency defaults to 75% of the certificate lifetime. This is configurable under Settings in the app.
11
11
12
-
In addition, as your certificate approaches expiration, the certificate authority (such as Let's Encrypt) may also email you. This can also happen if you have changed a certificate (for instance to add more domains to it) so you may get emails for expiring certificates you have since replaced.
12
+
The app includes a Certify background service which performs all the main function for managed certificates, so you don't need to leave the UI open for renewals etc to run.
13
+
14
+
## Monitoring Certificate Renewals
15
+
16
+
### Zero Config Status Reporting API
17
+
Unlike almost all other ACME clients, if the renewal process fails repeatedly, **the app API will try to notify you** via our API before certificate expiration becomes a problem, without any special configuration from yourself, unless you have disabled the *Enable Status Reports to Dashboard* option under Settings. **Ensure that your 'Certificate Authority Account' under Settings > Certificate Authorities is set to a real, monitored, email address** preferably accessible by others if you are a group of site administrators. You do not need to configure anything else like SMTP relays etc. to use this feature, it's all automatic by default.
18
+
19
+
In addition, as your certificate approaches expiration, the certificate authority (such as Let's Encrypt) *may* also email you. This can also happen if you have changed a certificate (for instance to add more domains to it) so you may get emails for expiring certificates you have since replaced.
20
+
21
+
### Certify Dashboard
22
+
You can optionally send reports to the certifytheweb.com [Dashboard](dashboard/index.md) when a renewal is successful or fails. This is useful if you have multiple system administrators and want to see when a renewal fails, or if you want to monitor renewal attempt status across many servers. You can see the status of all your certificates on the dashboard. To get started with sending reports to the Dashboard, select the *Add to Dashboard* option from the start up screen of the app on your machine.
13
23
14
24
## App Updates Are Important
15
25
16
26
If the app offers an update you should check the release notes to see if they sounds relevant to you and if in doubt you should update the app anyway. Certificate Authorities regularly change how their services work, and not updating the app can result in future renewal failures. We only support the latest version of the app at all times.
17
27
18
-
## Dashboard
19
-
You can optionally send reports to the https://certifytheweb.com dashboard when a renewal is successful or fails. This is useful if you have multiple administrators and want to be notified when a renewal fails. You can also see the status of all your certificates on the dashboard. To get started with sending reports to the Dashboard, select the *Add to Dashboard* option from the start up screen of the app on your machine.
20
-
21
28
## Certificate Cleanup
22
29
23
30
By default the app will remove certificates it has created (which have `[Certify]` in the 'friendly name') once they have been expired for over a month. This is to allow users who have manually allocated the certificate to other services to switch to the latest certificate before we delete the old one.
Copy file name to clipboardExpand all lines: docs/support.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,22 +9,24 @@ To get started using the Certify The Web, see the [Getting Started Guide](intro.
9
9
10
10
Check out our [FAQ](faq.md) if you are just getting started and having trouble with something.
11
11
12
-
If you'd just like to ask general questions or help others get started, check out our community forum: <ahref="https://community.certifytheweb.com"target="_blank">community.certifytheweb.com</a>
13
-
14
-
If there is a general bug or feature request you'd like to discuss in public, you can create a new issue against our <ahref="https://github.com/webprofusion/certify/issues"target="_blank">GitHub project</a>
15
-
16
12
## Commercial Support
17
13
18
14
**The application is ideal for organisations or professionals who need a tool with dependable support.**
19
15
20
16
_You are encouraged to test out the software yourself as an evaluation before purchasing as not all usage scenarios will be supported._
21
17
22
-
Full time support is available via email support tickets for registered users (or those who are evaluating the software). You can register for the Professional or Enterprise editions via https://certifytheweb.com/upgrade/.
18
+
Full time support is available via email support tickets for registered users (or those who are evaluating the software). You can register for the Professional or Enterprise editions via https://certifytheweb.com/upgrade/. To create a new support request for help or for general questions, email **support at certifytheweb.com**, including details of your licensed email address, describing the problem/question in detail with any supporting information you can provide.
19
+
20
+
- Please include how to recreate the problem and any special configuration you may have.
21
+
- Logs for managed certificates can be found on the Status tab of each managed certificate.
22
+
- Domain details shared with us via support are treated as confidential and there is no need to redact domains in logs etc (redacting domains can make issue diagnosis more difficult).
23
23
24
24
Support operates weekdays (Australian Western Standard Time) with some coverage on weekends. Telephone support and general consultancy is not currently available but we will try to help where we can for all questions.
25
25
26
-
Users of the free Community Edition are also supported via our community forum and github issues.
26
+
## Community Support
27
+
All users of the free Community Edition are encouraged to join our community forum: <ahref="https://community.certifytheweb.com"target="_blank">community.certifytheweb.com</a>
28
+
29
+
If there is a general bug or feature request you'd like to discuss in public, you can create a new issue against our <ahref="https://github.com/webprofusion/certify/issues"target="_blank">GitHub project</a> or discuss on the community forum.
30
+
27
31
28
-
To create a new support request for help or for general questions, email **support at certifytheweb.com**, including details of your licensed email address, describing the problem/question in detail with any supporting information you can provide.
29
32
30
-
Please include how to recreate the problem and any special configuration you may have. Logs for managed certificates can be found on the Status tab of each managed certificate. Domain details shared with us via support are treated as confidential and there is no need to redact domains in logs etc (redacting domains can make issue diagnosing more difficult).
0 commit comments