Fully qualified domain name → Caddy → home network (trivial newbie questions)

I run a support forum myself, so I know how irksome it can be when people ignore the template.

But my question is purely conceptual, so please forgive me for just cutting right to it.

I have set up Caddy for the 1st time, and have managed to get it mostly fulfilling my goals. But the truth is I barely comprehend what I’m doing. So I’ll likely have a few questions.

I run my own web server, so I’m using my own fully qualified domain name.


A record = proxy.domain.tld →

CNAME = files.domain.tld → proxy.domain.tld

CNAME = homeassistant.domain.tld → proxy.domain.tld

CNAME = media.domain.tld → proxy.domain.tld


The way I have everything configured right now, domain.tld gets a letsencrypt cert on my webserver (with wildcard support), and then each subdomain subsequently receives a letsencrypt cert from Caddy.

So my first question is: is this generally the best practice?

OR is it possible (and is there an argument in favor of) suppressing cert creation in Caddy and instead repurposing that original upstream cert?

Thank you for a great utility and for this support portal.

1 Like

I’m not sure I understand the problem you’re trying to solve. Why are you maintaining TLS certs outside of Caddy at all? Use Caddy to front all your services, that’s what it’s great at doing.

There’s definitely some context missing here; which is why the template is particularly useful, because knowing how you installed Caddy, what your config actually looks like, the version, logs, etc, all reduces the knowledge gap between us.

Hi Francis,

I appreciate the support which makes me hesitant to contradict you.

I am happy to share my config, and probably will at some point. But right now I’m asking a ‘big picture’ question and I fear that getting bogged down in the minutiae of my config would only serve to distract.

I haven’t described a problem yet.

Your response makes me realize that the setup I’m attempting may not be as common as I assumed it was, and it also makes me realize what I didn’t explain.

The “vanity” domain name (stev.land) I’m using for my internal network is one that I’ll also be using for my personal website, email, etc.

I like the idea of having one domain for all of my personal (non-business) stuff, from online entities (eg. blog.stev.land) to home services (plex.stev.land).

So that’s why I have an upstream letsencrypt cert.

I suppose I could register a separate domain name for my home network if you feel there is a compelling reason to do so.

Do you foresee any potential issues?

Well the point is that your config is what helps inform that “big picture”. That’s why we ask for it. We can’t be sure we’re talking about the same “big picture” unless we’re on the same page.

Are these hosted in different places? If they’re all in the same place (your home network) then you can just use Caddy to front it all.

No need, it’s fine to use the same domain for multiple purposes/servers.

It’s certainly easier/simpler to just let Caddy automate TLS. If you need you can issue a wildcard with Caddy as well using the DNS challenge.

If your existing certs (not from Caddy) are Let’s Encrypt with 90 day lifetimes, then you’d need to set up automation to copy the certs over to Caddy or whatever and that’s asking for trouble. The point of these tools is to allow you to get rid of that janky stuff. It’s best for certs to be automated as close to the server as possible (and in Caddy’s case, the server itself is the ACME client which is the optimal case).

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.