| Quellcodebibliothek Statistik Leitseite products/Sources/formale Sprachen/C/Apache/docs/manual/mod/ (Apache Software Stiftung Version 2.4.65©) Datei vom 10.6.2025 mit Größe 105 kB |
|
Quellcode-Bibliothek mod_md.html.en Sprache: unbekannt |
|
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DT <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /> <!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> <title>mod_md - Apache HTTP Server Version 2.4</title> <link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" titl <link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="al <link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/ <script src="../style/scripts/prettify.min.js" type="text/javascript"> </script> <link href="../images/favicon.ico" rel="shortcut icon" /></head> <body> <div id="page-header"> <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> <p class="apache">Apache HTTP Server Version 2.4</p> <img alt="" src="../images/feather.png" /></div> <div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> <div id="path"> <a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server< <div id="page-content"> <div id="preamble"><h1>Apache Module mod_md</h1> <div class="toplang"> <p><span>Available Languages: </span><a href="../en/mod/mod_md.html" title="English"> en </a> | <a href="../fr/mod/mod_md.html" hreflang="fr" rel="alternate" title="Français"> fr </a></p> </div> <table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Ma via the ACME protocol </td></tr> <tr><th><a href="module-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="module-dict.html#ModuleIdentifier">Module Identifier:</a></th><td>md_module</t <tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_md.c</td></tr> <tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in versio <h3>Summary</h3> <p> This module manages common properties of domains for one or more virtual hosts. Its serves two main purposes: for one, supervise/renew TLS certificates via the ACME protocol (<a href="https://tools.ietf.org/html/rfc8555">RFC 8555</a>). Certificates will be renewed by the module ahead of their expiration to account for disruption in internet services. There are ways to monitor the status of all certificates managed this way and configurations that will run your own notification commands on renewal, expiration and errors. </p><p> Second, mod_md offers an alternate OCSP Stapling implementation. This works with managed certificates as well as with certificates you configure yourself. OCSP Stapling is a necessary component for any https: site, influencing page load times and, depending on other setups, page availability. More in the stapling section below. </p><p> The default ACME Authority for managing certificates is <a href="https://letsencrypt.org/">Let's Encrypt</a>, but it is possible to configure another CA that supports the protocol. </p> <p>Simple configuration example:</p> <div class="note"><h3>TLS in a VirtualHost context</h3> <pre class="prettyprint lang-config">MDomain example.org <VirtualHost *:443> ServerName example.org DocumentRoot htdocs/a SSLEngine on # no certificates specification </VirtualHost></pre> <p> This setup will, on server start, contact <a href="https://letsencrypt.org/">Let's Encrypt</a> to request a certificate for the domain. If Let's Encrypt can verify the ownership of the domain, the module will retrieve the certificate and its chain, store it in the local file system (see <code class="directive"><a href="#mdstoredir">MDStoreDir</a></cod and provide it, on next restart, to <code class="module"><a href="../mod/mod_ssl.html">mod_ss </p><p> This happens while the server is already running. All other hosts will continue to work as before. While a certificate is not available, requests for the managed domain will be answered with a '503 Service Unavailable'. </p> </div> <div class="note"><h3>Prerequisites</h3> <p> This module requires <code class="module"><a href="../mod/mod_watchdog.html">mod_watchdog< </p><p> Certificate sign-up and renewal with Let's Encrypt requires your server to be reachable on port 80 (http:) and/or port 443 (https:) from the public internet. (Unless your server is configured to use DNS for challenges - more on that under 'wildcard certificates') </p><p> The module will select from the methods offered by Let's Encrypt. Usually LE offers challenges on both ports and DNS and Apache chooses a method available. </p><p> To determine which one is available, the module looks at the ports Apache httpd listens on. If those include port 80, it assumes that the http: challenge (named http-01) is available. If the server listens on port 443, the https: challenge (named tls-alpn-01) is also added to the list. (And if <code class="directive"><a href="#mdchallengedns01">MDChallengeDns01</a></c is configured, the challenge dns-01 is added as well.) </p><p> If your setup is not so straight forward, there are two methods available to influence this. First, look at <code class="directive"><a href="#mdportmap">MDPortMap</a></c if the server is behind a portmapper, such as a firewall. Second, you may override the module's guesswork completely by configuring <code class="directive"><a href="#mdcachallenges">MDCAChallenges</a></code> directly. </p> </div> <div class="note"><h3>https: Challenges</h3> <p> For domain verification via the TLS protocol `tls-alpn-01` is the name of the challenge type. It requires the Apache server to listen on port 443 (see <code class="directive"><a href="#mdportmap">MDPortMap</a></code> if you map that port to something else). </p><p> Let's Encrypt will open a TLS connection to Apache using the special indicator `acme-tls/1` (this indication part of TLS is called ALPN, therefore the name of the challenge. ALPN is also used by browsers to request a HTTP/2 connection). </p><p> As with the HTTP/2 protocol, to allow this, you configure: </p> <pre class="prettyprint lang-config">Protocols h2 http/1.1 acme-tls/1</pre> <p> And the `tls-alpn-01` challenge type is available. </p> </div> <div class="note"><h3>Wildcard Certificates</h3> <p> Wildcard certificates are possible, but not straight-forward to use out of the box. Let's Encrypt requires the `dns-01` challenge verification for those. No other is considered good enough. </p><p> The difficulty here is that Apache cannot do that on its own. As the name implies, `dns-01` requires you to show some specific DNS records for your domain that contain some challenge data. So you need to _write_ your domain's DNS records. </p><p> If you know how to do that, you can integrated this with mod_md. Let's say you have a script for that in `/usr/bin/acme-setup-dns` you configure Apache with: </p> <pre class="prettyprint lang-config">MDChallengeDns01 /usr/bin/acme-setup-dns</pre> <p> and Apache will call this script when it needs to setup/teardown a DNS challenge record for a domain. </p><p> Assuming you want a certificate for `*.mydomain.com`, mod_md will call: </p> <pre class="prettyprint lang-config">/usr/bin/acme-setup-dns setup mydomain.com challen # this needs to remove all existing DNS TXT records for # _acme-challenge.mydomain.com and create a new one with # content "challenge-data"</pre> <p> and afterwards it will call </p> <pre class="prettyprint lang-config">/usr/bin/acme-setup-dns teardown mydomain.com # this needs to remove all existing DNS TXT records for # _acme-challenge.mydomain.com</pre> </div> <div class="note"><h3>Monitoring</h3> <p> Apache has a standard module for monitoring: <code class="module"><a href="../mod/mod_status mod_md contributes a section and makes monitoring your domains easy. </p><p> You see all your MDs listed alphabetically, the domain names they contain, an overall status, expiration times and specific settings. The settings show your selection of renewal times (or the default), the CA that is used, etc. </p><p> The 'Renewal' column will show activity and error descriptions for certificate renewals. This should make life easier for people to find out if everything is all right or what went wrong. </p><p> If there is an error with an MD it will be shown here as well. This let's you assess problems without digging through your server logs. </p><p> There is also a new 'md-status' handler available to give you the MD information from 'server-status' in JSON format. You configure it as </p> <pre class="prettyprint lang-config"><Location "/md-status"> SetHandler md-status </Location></pre> <p> on your server. As with 'server-status' you will want to add authorization for this. </p><p> If you just want to check the JSON status of a specific domain, simply append that to your status url: </p> <pre class="prettyprint lang-config">> curl https://<yourhost>/md-status/another-domain.o { "name": "another-domain.org", "domains": [ "another-domain.org", "www.another-domain.org" ], ...</pre> <p> This JSON status also shows a log of activities when domains are renewed: </p> <pre class="prettyprint lang-config">{ "when": "Wed, 19 Jun 2019 14:45:58 GMT", "type": "progress", "detail": "The certificate for the managed domain has been renewed succe },{ "when": "Wed, 19 Jun 2019 14:45:58 GMT", "type": "progress", "detail": "Retrieving certificate chain for test-901-003-1560955549 },{ "when": "Wed, 19 Jun 2019 14:45:58 GMT", "type": "progress", "detail": "Waiting for finalized order to become valid" },{ "when": "Wed, 19 Jun 2019 14:45:50 GMT", "type": "progress", "detail": "Submitting CSR to CA for test-901-003-1560955549.org" }, ...</pre> <p> You will also find this information in the file `job.json` in your staging and, when activated, domains directory. This allows you to inspect these at any later point in time as well. </p><p> In addition, there is <code class="directive"><a href="#mdcertificatestatus">MDCertificate gives access to relevant certificate information in JSON format. </p> </div> <div class="note"><h3>Stapling</h3> <p> If you want to try the stapling in one Managed Domain alone at first, configure: </p> <pre class="prettyprint lang-config"><MDomain mydomain.net> MDStapling on </MDomain></pre> <p> and use the 'server-status' and/or <code class="directive"><a href="#mdmessagecmd">MDMessag see if Stapling information is there, how long it is valid, from where it came and when it will be refreshed. </p><p> If this all works to your satisfaction, you can switch it on for all your certificates or just your managed ones. </p><p> The existing stapling implementation by mod_ssl is used by many sites for years. There are two main differences between the mod_ssl and mod_md one: </p> <ol> <li>On demand vs. scheduled: mod_ssl retrieves the stapling information when it is requested, e.g. on a new connection. mod_md retrieves it right at server start and after 2/3rds of its lifetime.</li> <li>In memory vs. persisted: mod_ssl <em>can</em> persist this information, but most example configurations use a memory cache. mod_md always stores in the file system.</li> </ol> <p> If you are unlucky and restart your server during an outage of your CA's OCSP service, your users may no longer reach your sites. Without persistence your server cannot provide the client with the data and the client browser cannot get it as well, since the OCSP service is not responding. </p><p> The implementation in mod_md will have persisted it, load it again after restart and have it available for incoming connections. A day or two before this information expires, it will renew it, making it able to cope with a long OCSP service downtime. </p><p> Due to backward compatibility, the existing implementation in mod_ssl could not be changed drastically. For example, mod_ssl is unable to add a dependency to mod_watchdog without braking many existing installations (that do not load it). </p> </div> <div class="note"><h3>tailscale</h3> <p> Since version 2.4.14 of the module, you can use it to get certificates for your <a href="https://tailscale.com">tailscale</a> domains. </p> <pre class="prettyprint lang-config"><MDomain mydomain.some-thing.ts.net> MDCertificateProtocol tailscale MDCertificateAuthority file://localhost/var/run/tailscale/tailscaled.sock", </MDomain></pre> <p> Tailscale provides secure networking between your machines, where ever they are, and can provide domain names in the *.ts.net space for them. For those, it will then provide Let's Encrypt certificates as well, so you can open these domains in your browser securely. </p> <p> The directives listed above tell Apache to contact the local tailscale demon for obtaining and renewing certificates. This will only work for the domain name that tailscale assigns to your machine. </p> <p> Otherwise, these certificates work exactly like the ones retrieved via the ACME protocol from Lets Encrypt. You see them in status reporting and MDMessageCmd directives are executed for them as well. </p> <p> More details are <a href="https://github.com/icing/mod_md#tailscale"> available at the mod_md github documentation</a>. </p> <p> Note that this feature only works on machines where the tailscale demon provides a unix domain socket. This, so far, seems only the case on *nix systems. </p> </div> </div> <div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" clas <ul id="toc"> <li><img alt="" src="../images/down.gif" /> <a href="#mdactivationdelay">MDActivationDelay</ <li><img alt="" src="../images/down.gif" /> <a href="#mdbaseserver">MDBaseServer</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdcachallenges">MDCAChallenges</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdcertificateagreement">MDCertificate <li><img alt="" src="../images/down.gif" /> <a href="#mdcertificateauthority">MDCertificate <li><img alt="" src="../images/down.gif" /> <a href="#mdcertificatecheck">MDCertificateChec <li><img alt="" src="../images/down.gif" /> <a href="#mdcertificatefile">MDCertificateFile</ <li><img alt="" src="../images/down.gif" /> <a href="#mdcertificatekeyfile">MDCertificateKe <li><img alt="" src="../images/down.gif" /> <a href="#mdcertificatemonitor">MDCertificateMo <li><img alt="" src="../images/down.gif" /> <a href="#mdcertificateprotocol">MDCertificateP <li><img alt="" src="../images/down.gif" /> <a href="#mdcertificatestatus">MDCertificateSta <li><img alt="" src="../images/down.gif" /> <a href="#mdchallengedns01">MDChallengeDns01</a></ <li><img alt="" src="../images/down.gif" /> <a href="#mdchallengedns01version">MDChallengeD <li><img alt="" src="../images/down.gif" /> <a href="#mdcheckinterval">MDCheckInterval</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdcontactemail">MDContactEmail</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mddrivemode">MDDriveMode</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdexternalaccountbinding">MDExternalA <li><img alt="" src="../images/down.gif" /> <a href="#mdhttpproxy">MDHttpProxy</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdmatchnames">MDMatchNames</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdmember">MDMember</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdmembers">MDMembers</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdmessagecmd">MDMessageCmd</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdmuststaple">MDMustStaple</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdnotifycmd">MDNotifyCmd</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdomain">MDomain</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdomainsetsection"><MDomainSet></a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdportmap">MDPortMap</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdprivatekeys">MDPrivateKeys</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdprofile">MDProfile</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdprofilemandatory">MDProfileMandator <li><img alt="" src="../images/down.gif" /> <a href="#mdrenewmode">MDRenewMode</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdrenewwindow">MDRenewWindow</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdrequirehttps">MDRequireHttps</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdretrydelay">MDRetryDelay</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdretryfailover">MDRetryFailover</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdserverstatus">MDServerStatus</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdstapleothers">MDStapleOthers</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdstapling">MDStapling</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdstaplingkeepresponse">MDStaplingKee <li><img alt="" src="../images/down.gif" /> <a href="#mdstaplingrenewwindow">MDStaplingRene <li><img alt="" src="../images/down.gif" /> <a href="#mdstoredir">MDStoreDir</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdstorelocks">MDStoreLocks</a></li> <li><img alt="" src="../images/down.gif" /> <a href="#mdwarnwindow">MDWarnWindow</a></li> </ul> <h3>Bugfix checklist</h3><ul class="seealso"><li><a href="https://www.apache.org/dist/httpd/ <ul class="seealso"> <li><a href="#comments_section">Comments</a></li></ul></div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDActivationDelay" id="MDActivationDelay">MDA <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>How long to delay acti <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDActivationDelay <var>dura <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> <tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in ver </table> <p> </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDBaseServer" id="MDBaseServer">MDBaseServer</ <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Control if base serve <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDBaseServer on|off</code></ <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDBaseServer off</code></t <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> Controls if the base server, the one outside all VirtualHosts should be managed by mod_md or not. By default, it will not. For the very reason that it may have confusing side-effects. It is recommended that you have virtual hosts for all managed domains and do not rely on the global, fallback server configuration. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDCAChallenges" id="MDCAChallenges">MDCAChall <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Type of ACME challeng <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDCAChallenges <var>name</va <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDCAChallenges tls-alpn <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> Sets challenge types (in order of preference) when proving domain ownership. Supported by the module are the challenge methods 'tls-alpn-01', 'dns-01' and 'http-01'. The module will look at the overall configuration of the server to find out which methods can be used. </p><p> If the server listens on port 80, for example, the 'http-01' method is available. The prerequisite for 'dns-01' is a configured <code class="directive"><a href="#mdchallenged 'tls-alpn-01' is described above in 'https: Challenges'. </p><p> This auto selection works for most setups. But since Apache is a very powerful server with many configuration options, the situation is not clear for all possible cases. For example: it may listen on multiple IP addresses where some are reachable on `https:` and some not. </p><p> If you configure <code class="directive">MDCAChallenges</code> directly, this auto selection Instead, the module will use the configured challenge list when talking to the ACME server (a challenge type must be offered by the server as well). This challenges are examined in the order specified. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDCertificateAgreement" id="MDCertificateAgr <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>You confirm that you a Authority.</td></tr> <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDCertificateAgreement ac <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p>When you use mod_md to obtain a certificate, you become a customer of the CA (e.g. Let's Encrypt so that you understand what they offer and what they might exclude or require from you. mod_md cannot, by itself, agree to such a thing. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDCertificateAuthority" id="MDCertificateAut <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>The URL(s) of the ACME <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDCertificateAuthority <va <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDCertificateAuthority <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> The URL(s) where the CA offers its service. Instead of the actual URL, you may use 'letsencrypt' or 'buypass'. </p><p> If you configure more than one URL, each one is tried in a round-robin fashion after a number of failures. You can configure how quickly or delayed that happens via the <code class="directive">MDRetryDelay</code> and <code class="directive">MDRetryFailover</code> directives. The default setting makes a failover after about half a day of trying. </p><p> All other settings apply to each of these URLs. It is therefore not possible to have two with different <code class="directive">MDExternalAccountBinding</code>s, for example. </p><p> For testing, CAs commonly offer a second service URL. The 'test' service does not give certificates valid in a browser, but are more relaxed in regard to rate limits. This allows for verification of your own setup before switching to the production service URL. </p> <div class="example"><h3>LE Test Setup</h3><pre class="prettyprint lang-config">MDCertificate </div> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDCertificateCheck" id="MDCertificateCheck">M <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Set name and URL patte <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDCertificateCheck <var>nam <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> <tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in ver </table> <p> </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDCertificateFile" id="MDCertificateFile">MDC <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Specify a static cert <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDCertificateFile <var>path <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> This is used inside a <code class="directive"><a href="#mdomainset">MDomainSet</a></code> and spe the file holding the certificate chain for the Managed Domain. The matching key is specified via <code class="directive"><a href="#mdcertificatekeyfile">MDCertificate </p> <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"><MDomain mydomain.c MDCertificateFile /etc/ssl/my.cert MDCertificateKeyFile /etc/ssl/my.key </MDomain></pre> </div> <p> This is that equivalent of the mod_ssl <code class="directive"><a href="../mod/mod_ssl.html#sslcertificatefile">SSLCertificat has several uses. </p><p> If you want to migrate an existing domain, using static files, to automated Let's Encrypt certificates, for one. You define the <code class="directive"><a href="#mdomainset">MDomainSet</a></code>, add the files here and remo the <code class="directive"><a href="../mod/mod_ssl.html#sslcertificatefile">SSLCertifi your VirtualHosts. </p><p> This will give you the same as before, with maybe less repeating lines in your configuration. Then you can add <code class="directive"><a href="#mdrenewmode">MDRene 'always' to it and the module will get a new certificate before the one from the file expires. When it has done so, you remove the <code class="directive">MDCertificateFile</code> and reload the server. </p><p> Another use case is that you renew your Let's Encrypt certificates with another ACME clients, for example the excellent <a href="https://certbot.eff.org">certbot</a>. Then let your MDs point to the files from certbot and have both working together. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDCertificateKeyFile" id="MDCertificateKeyFi <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Specify a static priv <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDCertificateKeyFile <var>p <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> This is used inside a <code class="directive"><a href="#mdomainset">MDomainSet</a></code> and spe the file holding the private key for the Managed Domain. The matching certificate is specified via <code class="directive"><a href="#mdcertificatefile">MDCertif </p><p> This is that equivalent of the mod_ssl <code class="directive"><a href="../mod/mod_ssl.html#sslcertificatekeyfile">SSLCertifi </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDCertificateMonitor" id="MDCertificateMonit <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>The URL of a certifica <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDCertificateMonitor name <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDCertificateMonitor cr <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> This is part of the 'server-status' HTML user interface and has nothing to do with the core functioning itself. It defines the link offered on that page for easy checking of a certificate monitor. The SHA256 fingerprint of the certificate is appended to the configured url. </p><p> Certificate Monitors offer supervision of Certificate Transparency (CT) Logs to track the use of certificates for domains. The least you may see is that Let's Encrypt (or whichever CA you have configured) has entered your certificates into the CTLogs. </p><p> Caveat: certificate logs update and monitor's intakes of those updates suffer some delay. This varies between logs and monitors. A brand new certificate will not be known immediately. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDCertificateProtocol" id="MDCertificateProt <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>The protocol to use wi <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDCertificateProtocol <var> <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDCertificateProtocol A <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> Specifies the protocol to use. Currently, only <code>ACME</code> is supported. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDCertificateStatus" id="MDCertificateStatus <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Exposes public certi <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDCertificateStatus on|of <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDCertificateStatus on</ <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> When enabled, a resources is available in Managed Domains at 'https://domain/.httpd/certificate-status' that returns a JSON document list key properties of the current and of a renewed certificate - when available. </p> <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">{ "valid-until": "Thu, 29 Aug 2019 16:06:35 GMT", "valid-from": "Fri, 31 May 2019 16:06:35 GMT", "serial": "03039C464D454EDE79FCD2CAE859F668F269", "sha256-fingerprint": "1ff3bfd2c7c199489ed04df6e29a9b4ea6c015fe8a1b0ce3deb88afc75 "renewal" : { ...renewed cert information... } }</pre> </div> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDChallengeDns01" id="MDChallengeDns01">MDCha <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Set the command for se <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDChallengeDns01 <var>path- <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> Define a program to be called when the `dns-01` challenge needs to be setup/torn down. The program is given the argument `setup` or `teardown` followed by the domain name. For `setup` the challenge content is additionally given. When <code class="directive"><a href="#mdchallengedns01version">MDChallengeDns01Version</a></c the `teardown` also gets the challenge content as argument. </p><p> You do not need to specify this, as long as a 'http:' or 'https:' challenge method is possible. However, Let's Encrypt makes 'dns-01' the only challenge available for wildcard certificates. If you require one of those, you need to configure this. </p><p> It is now possible to use this directive inside a <code class="directive"><a href="#mdomain">MDo section to specify a specific command for that domain. This allows to configure a script specific for the particular DNS provider involved. </p><p> See the section about wildcard certificates above for more details. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDChallengeDns01Version" id="MDChallengeDns0 <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Set the type of argume <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDChallengeDns01Version 1 <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDChallengeDns01Versio <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> <tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in ver </table> <p> Set the way MDChallengeDns01 command is invoked, e.g the number and types of arguments. See <code class="directive"><a href="#mdchallengedns01">MDChallengeDns for the differences. This setting is global and cannot be varied per domain. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDCheckInterval" id="MDCheckInterval">MDCheck <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Determines how often <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDCheckInterval <var>durati <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDCheckInterval 12h</cod <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> <tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in ver </table> <p> The time between certificate checks. By default, the validity and need for renewals is checked twice a day. This interval is not followed precisely. Instead the module randomly applies a +/-50% jitter to it. With the default of 12 hours, this means the actual time between runs varies between 6 and 18 hours, jittered anew every run. This helps to mitigate traffic peaks at ACME servers. </p><p> The minimum duration you may configure is 1 second. It is not recommended to use such short times in production. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDContactEmail" id="MDContactEmail">MDContact <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Email address used fo <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDContactEmail <var>address< <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> <tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in ver </table> <p> The ACME protocol requires you to give a contact url when you sign up. Currently, Let's Encrypt wants an email address (and it will use it to inform you about renewals or changed terms of service). <code class="module"><a href="../mod/mod_md.html">mod_md</a></co your Apache configuration, so please specify the correct address there. If <code class="directive">MDContactEmail</code> is not present, <code class="module"><a href=" <code class="directive"><a href="../mod/core.html#serveradmin">ServerAdmin</a></code> direc </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDDriveMode" id="MDDriveMode">MDDriveMode</a> <a n <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>former name of MDRene <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDDriveMode always|auto|m <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDDriveMode auto</code></t <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p>This directive exists for backward compatibility as the old name for <code class="directive"><a href="#mdrenewmode">MDRenewMode</a></code>. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDExternalAccountBinding" id="MDExternalAcco <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Set the external acco <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDExternalAccountBinding < <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDExternalAccountBindi <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> <tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in ver </table> <p> Configure values for ACME "External Account Binding", a feature of the ACME standard that allows clients to bind registrations to an existing customer account on ACME servers. </p> <p> Let's Encrypt does not require those, but other ACME CAs do. Check with your ACME CA if you need those and how to obtain the values. They are two strings, a key identifier and a base64 encoded 'hmac' value. </p> <p> You can configure those globally or for a specific MDomain. Since these values allow anyone to register under the same account, it is advisable to give the configuration file restricted permissions, e.g. root only. </p> <p> The value can also be taken from a JSON file, to keep more open permissions on the server configuration and restrict the ones on that file. The JSON itself is: </p> <div class="example"><h3>EAB JSON Example file</h3><pre class="prettyprint lang-config">{"kid" </div> <p> If you change EAB values, the new ones will be used when the next certificate renewal is due. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDHttpProxy" id="MDHttpProxy">MDHttpProxy</a> <a n <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Define a proxy for out <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDHttpProxy <var>url</var></co <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p>Use a http proxy to connect to the <code class="directive"><a href="#mdcertificateauthority"> if your webserver can only reach the internet with a forward proxy. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDMatchNames" id="MDMatchNames">MDMatchNames</ <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Determines how DNS na <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDMatchNames all|serverna <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDMatchNames all</code></t <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> <tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in ver </table> <p> The mode `all` is the behaviour as in all previous versions. Both ServerName and ServerAlias are inspected to find the MDomain matching a VirtualHost. This automatically detects coverage, even when you only have added one of the names to an MDomain. </p><p> However, this auto-magic has drawbacks in more complex setups. If you set this directive to `servernames`, only the ServerName of a virtual host is used for matching. ServerAliases are disregarded then, for matching. Aliases will still be added to the certificate obtained, unless you also run `MDMembers manual`. </p><p> Another advantage of `servernames` is that it gives you more flexibility with sub-domains and wildcards. You can define one MDomain with a wildcard and have other MDomains for specific sub-domain names. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDMember" id="MDMember">MDMember</a> <a name="mdme <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Additional hostname <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDMember <var>hostname</var></ <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> Instead of listing all dns names on the same line, you may use <code class="directive">MDMember</code> to add such names to a managed domain. </p> <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"><MDomain example.or MDMember www.example.org MDMember mail.example.org </MDomain></pre> </div> <p> If you use it in the global context, outside a specific MD, you can only specify one value, 'auto' or 'manual' as the default for all other MDs. See <code class="directive"><a href="#mdomain">MDomain</a></code> for a description of these special values. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDMembers" id="MDMembers">MDMembers</a> <a name="m <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Control if the alias d <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDMembers auto|manual</cod <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDMembers auto</code></td></ <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p>Defines if the <code class="directive"><a href="../mod/core.html#servername">ServerName</ <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> value are automatically added to the members of a Managed Domain or not. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDMessageCmd" id="MDMessageCmd">MDMessageCmd</ <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Handle events for Man <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDMessageCmd <var>path-to-c <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> This command gets called when one of the following events happen for a Managed Domain: "renewed", "installed", "expiring", "errored". The command may be invoked for more than these in the future and ignore events it is not prepared to handle. </p><p> This is the more flexible companion to <code class="directive"><a href="#mdnotifycmd">MDNotif </p> <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">MDMessageCmd /etc/ <p><code> # will be invoked when a new certificate for mydomain.org is available as: /etc/apache/md-message renewed mydomain.com </code></p></div> <p> The program should not block, as the module will wait for it to finish. A return code other than 0 is regarded as an error. </p><p> 'errored' is no immediate cause for concern since renewal is attempted early enough to allow the internet to come back. This is reported at most once per hour. </p><p> 'expiring' should be taken serious. It is issued when the <code class="directive"><a href="#mdwarnwindow">MDWarnWindow</a></code> is reached. By default 10% of the certificate lifetime, so for Let's Encrypt this currently means 9 days before it expires. The warning is repeated at most once a day. </p><p> 'renewed' means that a new certificate has been obtained and is stored in the 'staging' area in the MD store. It will be activated on the next server restart/reload. </p><p> 'installed' is triggered when a new certificate has been transferred from staging into the domains location in MD store. This happens at server startup/reload. Different to all other invocations, <code class="directive">MDMessageCmd</ with root permissions (on *nix systems) and has access to the certificate files (and keys). Certificates needed for other applications or in different formats can be processed on this event. </p><p> 'renewing' event is triggered before starting renew process for the managed domain. Should the command return != 0 for this reason, renew will be aborted and repeated on next cycle. Some cluster setups use this to allow renewals to run only on a single node. </p><p> 'challenge-setup:type:domain' event is triggered when the challenge data for a domain has been created. This is invoked before the ACME server is told to check for it. The type is one of the ACME challenge types. This is invoked for every DNS name in a MDomain. Cluster setups may use this event to distribute challenge files to all nodes in a cluster. </p><p> ocsp-errored happens when <code class="directive"><a href="#mdstapling">MDStapling</a></code> is enabled for a domain, this indicates that an error was encountered retrieving the OCSP response from the Certificate Authority. mod_md will continue trying. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDMustStaple" id="MDMustStaple">MDMustStaple</ <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Control if new certif <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDMustStaple on|off</code></ <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>MDMustStaple off</code></t <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p>Defines if newly requested certificate should have the OCSP Must Staple flag set or not. If a certificate has this flag, the server is required to send a OCSP stapling response to every client. This only works if you configure <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> to generate this (see <cod and friends). </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDNotifyCmd" id="MDNotifyCmd">MDNotifyCmd</a> <a n <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Run a program when a Ma <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDNotifyCmd <var>path</var> [ <v <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> The configured executable is run when a Managed Domain has signed up or renewed its certificate. It is given the name of the processed MD as additional arguments (after the parameters specified here). It should return status code 0 to indicate that it has run successfully. </p> </div> <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="directive-section"><h2><a name="MDomain" id="MDomain">MDomain</a> <a name="mdomain <table class="directive"> <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Define list of domain <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>MDomain <var>dns-name</var> [ <v <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Experimental</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_md</td></tr> </table> <p> All the names in the list are managed as one Managed Domain (MD). mod_md will request one single certificate that is valid for all these names. This --> -------------------- --> maximum size reached --> -------------------- [ 0.41Quellennavigators Projekt ] |
2026-04-02