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: README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -178,7 +178,7 @@ copying private key to ssh:server5:/home/yourdomain/ssl/domain.key
178
178
copying CA certificate to ssh:server5:/home/yourdomain/ssl/chain.crt
179
179
reloading SSL services
180
180
```
181
-
This will (by default) used the staging server, so should give you a certificate that isn't trusted ( Fake Let's Encrypt).
181
+
This will (by default) use the staging server, so should give you a certificate that isn't trusted ( Fake Let's Encrypt).
182
182
Change the server in your config file to get a fully valid certificate.
183
183
184
184
Note: Using DNS validation is now working successfully for issuing certificates. (examples provided on the wiki pages - https://github.com/srvrco/getssl/wiki/DNS-Challenge-example )
@@ -189,11 +189,11 @@ I use the following cron
189
189
```
190
190
23 5 * * * /root/scripts/getssl -u -a -q
191
191
```
192
-
The cron will automatically update getssl and renew any certificates, only giving output if anything happens.
192
+
The cron will automatically update getssl and renew any certificates, only giving output if there are issues / errors.
193
193
194
194
* The -u flag updates getssl if there is a more recent version available.
195
195
* The -a flag automatically renews any certificates that are due for renewal.
196
-
* The -q flag is "quiet" so that it only outputs and emails me if any certificates were updated, or there was an error / issue.
196
+
* The -q flag is "quiet" so that it only outputs and emails me if there was an error / issue.
197
197
198
198
## Issues / problems / help
199
199
If you have any issues, please log them at https://github.com/srvrco/getssl/issues
0 commit comments