@@ -285,44 +285,6 @@ MDChallengeDns01 /usr/bin/acme-setup-dns
285285 </p >
286286 </note >
287287
288- <note ><title >tailscale</title >
289- <p >
290- Since version 2.4.14 of the module, you can use it to get certificates
291- for your <a href =" https://tailscale.com" >tailscale</a > domains.
292- </p >
293- <highlight language =" config" >
294- < MDomain mydomain.some-thing.ts.net>
295- MDCertificateProtocol tailscale
296- MDCertificateAuthority file://localhost/var/run/tailscale/tailscaled.sock",
297- < /MDomain>
298- </highlight >
299- <p >
300- Tailscale provides secure networking between your machines, where ever
301- they are, and can provide domain names in the *.ts.net space for them.
302- For those, it will then provide Let's Encrypt certificates as well, so
303- you can open these domains in your browser securely.
304- </p >
305- <p >
306- The directives listed above tell Apache to contact the local tailscale
307- demon for obtaining and renewing certificates. This will only work for
308- the domain name that tailscale assigns to your machine.
309- </p >
310- <p >
311- Otherwise, these certificates work exactly like the ones retrieved
312- via the ACME protocol from Lets Encrypt. You see them in status reporting
313- and MDMessageCmd directives are executed for them as well.
314- </p >
315- <p >
316- More details are <a href =" https://github.com/icing/mod_md#tailscale" >
317- available at the mod_md github documentation</a >.
318- </p >
319- <p >
320- Note that this feature only works on machines where the tailscale
321- demon provides a unix domain socket. This, so far, seems only the
322- case on *nix systems.
323- </p >
324- </note >
325-
326288 </summary >
327289
328290 <directivesynopsis >
0 commit comments