you are viewing a single comment's thread
view the rest of the comments
[–] 23 points 9 months ago (6 children)

I do not understand why you are using certwarden when Caddy can generate SSL certificates by itself.

  • source
  • hideshow 6 child comments
  • [+] [S] 4 points 9 months ago (6 children)
  • [–] 13 points 9 months ago (1 child)

    But you're still using Caddy as the sole reverse proxy, don't you? Do you have multiple Caddy instances that require access to a single certificate?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 9 months ago

    Thing is, you may have some devices that should be accessible even if the reverse proxy is unreachable.
    And if you have HSTS and wamt to reach a device under the same local DNS suffix (example: External -> service.example.org, Internal: service.int.examole.org) you can't just bypass the https warning.
    Same for devices reachable over RDP, SSH, etc. etc.

  • source
  • parent
  • [–] 7 points 9 months ago (3 children)

    If you switch to the dns-01 challenge you can just generate the certs on multiple servers hasselfree. And as a bonus you can get wildcard certs for subdomains.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 9 months ago* (2 children)

    How ?

    I've seen nothing about that in the Caddy docs.

    I must admit that one disadvantage of Caddy compared to when I was using acme.sh, is having to make a request to Let's Encrypt (even automatically) for every subdomain, making all of them visible on crt.sh

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (-1 replies)