Template:Let’s Encrypt/New Cert Command: Difference between revisions

From wiki
VisualWikitext
Created page with "<noinclude> == Description == <templatedata> { "description": "Warning about instructions applying only to the Debian distribution", "params": { "domain": { "descriptio..."
 
Make post command optional
 
(10 intermediate revisions by the same user not shown)
Line 3: Line 3:
<templatedata>
<templatedata>
{
{
"description": "Warning about instructions applying only to the Debian distribution",
"description": "Show Let’s Encrypt command to create a new certificate",
"params": {
"params": {
"domain": {
"domain": {
"description": "For wich domain will you certificate be issued",
"description": "For which domain will you certificate be issued",
"example": "wiki.example.com",
"example": "wiki.example.com",
"type": "string",
"type": "string",
Line 15: Line 15:
"example": "service nginx restart",
"example": "service nginx restart",
"type": "string",
"type": "string",
"required": true
"suggested": true
},
"beforeCommand": {
"label": "Before Command",
"description": "Command to be run before getting the certificate",
"example": "# service nginx reload",
"type": "string"
}
}
}
}
Line 22: Line 28:


== Example ==
== Example ==
<nowiki>{{Let’s Encrypt New Cert|domain=example.com|command=service nginx reload}}</nowiki>
<nowiki>{{Let’s Encrypt/New Cert Command|domain=example.com|command=service nginx reload}}</nowiki>
 
{{Let’s Encrypt/New Cert Command|domain=example.com|command=service nginx reload}}
{{Let’s Encrypt New Cert|domain=example.com|command=service nginx reload}}
</noinclude><includeonly>{{#tag:syntaxhighlight|
</noinclude><includeonly>
{{#if: {{{beforeCommand|}}} | {{{beforeCommand}}} }}
{{#tag:syntaxhighlight|# /usr/local/sbin/renew_certificates
$ sudo /usr/local/sbin/certmanage
Renewing certificate for {{{domain}}} that will expire on 0001-01-01
Renewing certificate for {{{domain}}} that will expire on 0001-01-01


 
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for {{{domain}}}
Using the webroot path /var/www/acme-challenge for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Generating key (2048 bits): /etc/letsencrypt/keys/1764_key-certbot.pem
Creating CSR: /etc/letsencrypt/csr/1764_csr-certbot.pem


IMPORTANT NOTES:
IMPORTANT NOTES:
  - Congratulations! Your certificate and chain have been saved at
  - Congratulations! Your certificate and chain have been saved at
   /etc/letsencrypt/live/{{{domain}}}/fullchain.pem. Your
   /etc/letsencrypt/live/{{{domain}}}/fullchain.pem. Your cert
   cert will expire on {{#time: Y-m-d | now + 90 day}}. To obtain a new version of the
   will expire on {{#time: Y-m-d | now + 90 day}}. To obtain a new or tweaked version of
   certificate in the future, simply run Let's Encrypt again.
   this certificate in the future, simply run certbot again. To
  - If you like Let's Encrypt, please consider supporting our work by:
  non-interactively renew *all* of your certificates, run "certbot
  renew"
  - If you like Certbot, please consider supporting our work by:


   Donating to ISRG / Let's Encrypt:  https://letsencrypt.org/donate
   Donating to ISRG / Let's Encrypt:  https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le
   Donating to EFF:                    https://eff.org/donate-le


Restarting services:
{{#if: {{{command|}}} | Restarting services:
{{command}}
{{{command}}} }}
|lang="console"}}
|lang="console"}}</includeonly>
</includeonly>

Latest revision as of 09:41, 2 April 2017

Description

Show Let’s Encrypt command to create a new certificate

Template parameters[Edit template data]

ParameterDescriptionTypeStatus
domaindomain

For which domain will you certificate be issued

Example
wiki.example.com
Stringrequired
commandcommand

Command to be run after certificate creation

Example
service nginx restart
Stringsuggested
Before CommandbeforeCommand

Command to be run before getting the certificate

Example
# service nginx reload
Stringoptional

Example

{{Let’s Encrypt/New Cert Command|domain=example.com|command=service nginx reload}} 

$ sudo /usr/local/sbin/certmanage
Renewing certificate for example.com that will expire on 0001-01-01

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for example.com
Using the webroot path /var/www/acme-challenge for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Generating key (2048 bits): /etc/letsencrypt/keys/1764_key-certbot.pem
Creating CSR: /etc/letsencrypt/csr/1764_csr-certbot.pem

IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at
   /etc/letsencrypt/live/example.com/fullchain.pem. Your cert
   will expire on 2025-07-20. To obtain a new or tweaked version of
   this certificate in the future, simply run certbot again. To
   non-interactively renew *all* of your certificates, run "certbot
   renew"
 - If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le

Restarting services:
service nginx reload
Retrieved from "https://wiki.meurisse.org/index.php?title=Template:Let’s_Encrypt/New_Cert_Command&oldid=571"