8 ms·

Caddy[0] also uses ZeroSSL[1] alongside Let’s Encrypt. [0] https://caddyserver.com/docs/automatic-https#overview https://caddyserver.com/docs/automatic-https#o

Caddy[0] also uses ZeroSSL[1] alongside Let’s Encrypt. [0] https://caddyserver.com/docs/automatic-https#overview https://caddyserver.com/docs/automatic-https#overview [1] https://zerossl.com/ https://zerossl.com/

sam_goody 5y ago
Caddy and ZeroSSL are the same company, "Stack Holdings GmbH". It used to be prominent on the respective pages, but is now stated in the footer.
- joshxyz 5y ago
  thats a big TIL caddy is actually great! auto ssl
  - boramalper 5y ago
    Same here! I think it was ZeroSSL that bought Caddy now that I remember.
    - francislavoie 5y ago
      The announcement is here: https://caddy.community/t/caddy-and-certmagic-have-new-ownership-no-changes-to-licensing-or-development/9754 https://caddy.community/t/caddy-and-certmagic-have-new-owner...
- tnolet 5y ago
  We use Caddy for serving our free dashboards and status pages on your own domain at https://checklyhq.com https://checklyhq.com It was not super easy to set up. I think the whole config is 20 lines or so, but the docs, naming and functionality of how Caddy actually interfaces with LE was tricky to find out. Basically had to scrape together answers from various GitHub issues etc. I should write a blog post… Edit: now it runs fine btw
  - francislavoie 5y ago
    What did you find unclear, specifically? We encourage users to come ask for help on our forums, we'll gladly explain everything you need to know. https://caddy.community https://caddy.community
    - tnolet 5y ago
      Hey Francis, let me go back to the project. I managed to stitch together our use case by reading - https://caddy.community/t/https-for-dynamic-subdomains-and-custom-domains/7921/4 https://caddy.community/t/https-for-dynamic-subdomains-and-c... - https://caddy.community/t/best-practise-for-multiple-tenant-multiple-https-domain-server/2082 https://caddy.community/t/best-practise-for-multiple-tenant-... and various GitHub issues Our use case was: "serve SSL certificates on the fly for users hitting :443 AND users hitting *.checklyhq.com, then proxy some content." The documentation looks visually nice, but is hard to parse as the layout of the config file (and the hierarchy of the items in it) is separate from the explanation of what they do. I was continuously doing a Ctr+F to find words on the page. Example: https://caddyserver.com/docs/caddyfile/options https://caddyserver.com/docs/caddyfile/options Here the stanzas are clickable. https://caddyserver.com/docs/caddyfile/directives/tls https://caddyserver.com/docs/caddyfile/directives/tls Here not. Last thing. The docs present a lot of config examples in snippets, but seeing how to use them in a full, syntactically correct file was hard. I felt I was missing the big picture. Sorry to not be more concrete, it was some time ago.
      - mholt 5y ago
        Francis has implemented your suggestions
      - francislavoie 5y ago
        I think if you had found your way to this article in the wiki https://caddy.community/t/serving-tens-of-thousands-of-domains-over-https-with-caddy/11179 https://caddy.community/t/serving-tens-of-thousands-of-domai... you would have had an easier time. The On-Demand TLS section in the docs now links to there (as of only a week or two ago) https://caddyserver.com/docs/automatic-https#on-demand-tls https://caddyserver.com/docs/automatic-https#on-demand-tls Regarding clickable bits in the docs, those are set up with some JS I wrote which tries to dynamically add links to certain things. I only set it up for Caddyfile directives and for the global options page in particular. Our docs are in markdown so any linking of things needs to be wired up after the fact on page load with some vanilla JS. I'll look into improving that for some more pages. Thanks for the feedback!
eliaspro 5y ago
It also automatically handles a fail-over in case a CA is not available: https://caddyserver.com/docs/automatic-https#issuer-fallback https://caddyserver.com/docs/automatic-https#issuer-fallback
leo_bloom 5y ago
Ah of course, a HN thread about TLS/SSL/webservers wouldn't be complete without someone exclaiming their love for Caddy. We get it, it's the bestest server ever.
- francislavoie 5y ago
  It's relevant to the discussion. No other server with ACME supports multiple issuers by default. It speaks directly to the point being made in the linked article (and other previous articles written by Scott).
  - diftraku 5y ago
    For what it's worth, Traefik does allow you to change the server you talk to (it's just the staging server for LE they use in the example): https://doc.traefik.io/traefik/v2.0/https/acme/#caserverand https://doc.traefik.io/traefik/v2.0/https/acme/#caserverand A quick google does suggest that at least one person has tried using ZeroSSL with Traefik: https://spad.uk/get-free-zerossl-certs-using-traefik/ https://spad.uk/get-free-zerossl-certs-using-traefik/
    - francislavoie 5y ago
      Yes you can configure Traefik with other issuers, but it does not support having multiple configured at the same time and failing over between them in case something goes wrong. That's the point being made in the article. Caddy does this.

sam_goody 5y ago

Caddy and ZeroSSL are the same company, "Stack Holdings GmbH". It used to be prominent on the respective pages, but is now stated in the footer.

joshxyz 5y ago
thats a big TIL caddy is actually great! auto ssl
- boramalper 5y ago
  Same here! I think it was ZeroSSL that bought Caddy now that I remember.
  - francislavoie 5y ago
    The announcement is here: https://caddy.community/t/caddy-and-certmagic-have-new-ownership-no-changes-to-licensing-or-development/9754 https://caddy.community/t/caddy-and-certmagic-have-new-owner...
tnolet 5y ago
We use Caddy for serving our free dashboards and status pages on your own domain at https://checklyhq.com https://checklyhq.com It was not super easy to set up. I think the whole config is 20 lines or so, but the docs, naming and functionality of how Caddy actually interfaces with LE was tricky to find out. Basically had to scrape together answers from various GitHub issues etc. I should write a blog post… Edit: now it runs fine btw
- francislavoie 5y ago
  What did you find unclear, specifically? We encourage users to come ask for help on our forums, we'll gladly explain everything you need to know. https://caddy.community https://caddy.community
  - tnolet 5y ago
    Hey Francis, let me go back to the project. I managed to stitch together our use case by reading - https://caddy.community/t/https-for-dynamic-subdomains-and-custom-domains/7921/4 https://caddy.community/t/https-for-dynamic-subdomains-and-c... - https://caddy.community/t/best-practise-for-multiple-tenant-multiple-https-domain-server/2082 https://caddy.community/t/best-practise-for-multiple-tenant-... and various GitHub issues Our use case was: "serve SSL certificates on the fly for users hitting :443 AND users hitting *.checklyhq.com, then proxy some content." The documentation looks visually nice, but is hard to parse as the layout of the config file (and the hierarchy of the items in it) is separate from the explanation of what they do. I was continuously doing a Ctr+F to find words on the page. Example: https://caddyserver.com/docs/caddyfile/options https://caddyserver.com/docs/caddyfile/options Here the stanzas are clickable. https://caddyserver.com/docs/caddyfile/directives/tls https://caddyserver.com/docs/caddyfile/directives/tls Here not. Last thing. The docs present a lot of config examples in snippets, but seeing how to use them in a full, syntactically correct file was hard. I felt I was missing the big picture. Sorry to not be more concrete, it was some time ago.
    - mholt 5y ago
      Francis has implemented your suggestions
    - francislavoie 5y ago
      I think if you had found your way to this article in the wiki https://caddy.community/t/serving-tens-of-thousands-of-domains-over-https-with-caddy/11179 https://caddy.community/t/serving-tens-of-thousands-of-domai... you would have had an easier time. The On-Demand TLS section in the docs now links to there (as of only a week or two ago) https://caddyserver.com/docs/automatic-https#on-demand-tls https://caddyserver.com/docs/automatic-https#on-demand-tls Regarding clickable bits in the docs, those are set up with some JS I wrote which tries to dynamically add links to certain things. I only set it up for Caddyfile directives and for the global options page in particular. Our docs are in markdown so any linking of things needs to be wired up after the fact on page load with some vanilla JS. I'll look into improving that for some more pages. Thanks for the feedback!

eliaspro 5y ago

It also automatically handles a fail-over in case a CA is not available: https://caddyserver.com/docs/automatic-https#issuer-fallback https://caddyserver.com/docs/automatic-https#issuer-fallback

leo_bloom 5y ago

Ah of course, a HN thread about TLS/SSL/webservers wouldn't be complete without someone exclaiming their love for Caddy. We get it, it's the bestest server ever.

francislavoie 5y ago
It's relevant to the discussion. No other server with ACME supports multiple issuers by default. It speaks directly to the point being made in the linked article (and other previous articles written by Scott).
- diftraku 5y ago
  For what it's worth, Traefik does allow you to change the server you talk to (it's just the staging server for LE they use in the example): https://doc.traefik.io/traefik/v2.0/https/acme/#caserverand https://doc.traefik.io/traefik/v2.0/https/acme/#caserverand A quick google does suggest that at least one person has tried using ZeroSSL with Traefik: https://spad.uk/get-free-zerossl-certs-using-traefik/ https://spad.uk/get-free-zerossl-certs-using-traefik/
  - francislavoie 5y ago
    Yes you can configure Traefik with other issuers, but it does not support having multiple configured at the same time and failing over between them in case something goes wrong. That's the point being made in the article. Caddy does this.