92
edits
Setting Up Wildcard Subdomains with SSL on a Debian Application: Difference between revisions
Jump to navigation
Jump to search
m
Setting Up Wildcard Subdomains with SSL on a Debian Application (view source)
Revision as of 05:54, 31 October 2024
, 31 October 2024→b. Setting Up Certbot and Requesting Certificates
No edit summary |
|||
| Line 174: | Line 174: | ||
</pre> | </pre> | ||
This block registers Certbot, checks for an existing certificate, and if none exists, requests a new certificate using DNS authentication with the specified dns-auth.conf file. The --deploy-hook option calls the cert-deploy file after each certificate issuance or renewal. We will create the cert-deploy in step | This block registers Certbot, checks for an existing certificate, and if none exists, requests a new certificate using DNS authentication with the specified dns-auth.conf file. The --deploy-hook option calls the cert-deploy file after each certificate issuance or renewal. We will create the cert-deploy in [[https://docs.delftsolutions.nl/wiki/Setting_Up_Wildcard_Subdomains_with_SSL_on_a_Debian_Application#f._Creating_the_cert-deploy_Deploy_Hook|step f]]. | ||
In the case of our guide with the kaboom-api example, <code><CERT_NAME></code> is <code>kaboom-elearning</code>, again it's up to you to select the right naming for your case. | In the case of our guide with the kaboom-api example, <code><CERT_NAME></code> is <code>kaboom-elearning</code>, again it's up to you to select the right naming for your case. | ||