Issues with https certs locally

Spiffyman@slrpnk.net · 26 days

I have a minipc with proxmox on it. I have tried caddy in a lxc to set up DNS challenges to my owned domain and I set the url in my router to point to the IP (for example, proxmox.DOMAIN.com could be 192.168.10.22). The hope was to have everything local within my house and nothing needs the internet to be accessed. Some services I can host in proxmox NEED https to use, which I could not get working with my own certs or ones proxmox could make, thus Caddy. However, I get proxmox with a proper cert, but i cannot get any of the other services from proxmox working. If I were doing it all manually, I would expect DNS issues with the domain, but from what I understand, Caddy by default does wildcard domains which should mean that my services should work. but they do not. Networking is new to me so perhaps I am missing something obvious. Any guidance would be appreciated.

ShortN0te@lemmy.ml · 26 days

Short answer, it should work as you describe, everything local, no need to expose anything.

More information is needed to help.

Its either the caddy setup, maybe proxmox internal networking? Or most likely DNS, its almost always DNS.

valar@lemmy.ca · 26 days

IME Caddy will not do wildcard domains “by default” if you just configure sub.domain.com {} for everything. It will try to create a unique cert for each. You have to specifically configure it to use a wildcard cert.

DarkSirrush@piefed.ca · 25 days

Yeah it will, if you have even a single reference to a wildcard, preferably as one of your first entries in your caddyfile.

https://caddyserver.com/docs/automatic-https

You can literally get a wildcard cert by putting in the following entry, before any other routing logic:

*.domain.tld {
  respond "Wildcard Bitch!"
}

moonshine69@lemmy.nz · 24 days

If you are doing a dns challenge then You need to give caddy access to your domain to perform the dns challenge. Depending on domain provider that is easy or hard. It will briefly change some records that tells let’s encrypt you own the domain and then issue the cert

Or you can do http challenge, this requires you to manually configure your domain to point to a publicly accessible caddy endpoint which is probably not what you want, maybe there is a way to make it work through a cloud flare tunnel

Who is your domain provider?

Lem453@lemmy.ca · 24 days

This is for traefik but might help to understand the process and change it for caddy (https://youtu.be/liV3c9m_OX8)

You should have

Service.local.domain.com

For local only services (Vaultwarden) and

Service.domain.com

For external things (immich)

I’m your router / Pihole locally, you setup the above URLs to point to the IP of caddy

fundbasis_bot@lemmy.1095.me · 25 days

Two things that I think are tripping you up:

DNS. Your router only maps proxmox.DOMAIN.com to 192.168.10.22. The other services (in LXCs, with their own container IPs) resolve to nothing, so the browser can’t reach Caddy for them at all - that’s why Proxmox works and the rest don’t. Either add a record per service name pointing at the right IP, or forward those service ports into Caddy.
Certs. If you want to stay fully local (nothing needs the internet), skip DNS challenges entirely: Caddy has a built-in CA (tls internal in the site block). It auto-issues self-signed certs for whatever hostname you hit, no challenge, no DNS. You do need to export that CA and install it as a trusted root on the machines you browse from, but after that every service works with zero DNS configuration.

Wildcard aside: DNS-01 + wildcard only covers issuance, it doesn’t fix the resolution gap in point 1.

If you’re open to egress, a quick tunnel (cloudflared) removes cert management completely - Cloudflare terminates TLS on a random public URL. That’s how I expose a small self-hosted API of mine; the trade-off is the URL changes on every tunnel restart.

valkyre09@lemmy.world · 25 days

+1 for cloudflare tunnels. But if you want to host locally, nginx proxy manager has a very intuitive gui you’ll be able to host your sites on.

Example:

Docker container exposes port 8989 for sonarr. Nginx proxy manager entry will be: Sonarr.mydomain.com > http://192.168.0.50:8888/ There’s a setting to allow ssl for your domain.

In your domain registrar, just put the a record for sonarr.mydomain.com to the local IP of nginx proxy manager, in this case let’s assume it’s the same IP as sonarr.

So now in your house your computer calls the domain, your dns server responds with 192.168.0.50. That’s the IP of your proxy.

Your proxy gets your request. Sees you’re trying to access sonarr, and passes your query along to it.

But like I said, cloudflare tunnels removes ALL of this and even supports google / azure SSO to keep you secure and keep logins convenient.

non_burglar@lemmy.world · 26 days

or ones proxmox could make

In proxmox, ACME is a service for the root CA of the cluster. It does use letsencrypt, but it does not provide certs for clients.

Sounds like you are probably conflating DNS and PKI certificates.

stratself@lemdro.id · 25 days

Caddy does certs by responding to ACME challenges on port 80 and 443. You need to forward those ports from the public internet back to Caddy, have you done that?

Edit: it seems like you’re doing DNS challenges. Did you compile Caddy yourself with the right plugins? Have you tested the API token work? Any Caddy logs?

darvocet@infosec.pub · 26 days

Satan could help you little boy. Do you want working acme dns certs for everything? No more port 80 for anything if you just make a small arrangement with the devil.

The devil btw is AI, probably even self hostable. The new qwen model pretty solid if you have some hardware to run it on.