For instance how can I use my *.domain.com SSL certs and NPM to route containers to a subdomain without exposing them? The main domain is exposed.
Split DNS on your LAN?
Only records permitted to be access on your LAN are responded by a local DNS server. While public DNS still available for your public facing services.
Your wildcard cert will work for both situations as the browser only cares the sni matches the Url in your address bar.
I’m using this right now but I’m switching to having all my services under one domain and blocking non internal ips. Technically someone can access your site by providing the host manually, althought it’s unlikely since they would need to know it
Would you expanding in this concern? I’m not sure I understand but I’d like to.
You can use the DNS verification method. Either using nsupdate with bind or what ever protocol your DNS provider and favorite ACME (certbot, acme, lego, etc) utility supports. As long as your DNS server is publically reachable that will work, even if the subdomain itself doesn’t exist publically.
This is what I do as well. I have a public DNS record for my internal reverse proxy IP (no need to expose my public IP and associate it with my domain). I let NPM reach out to the DNS provider to complete verification challenge using an account token, NPM can then get a valid cert from Let’s Encrypt and nothing is exposed. All inbound traffic on 80/443 remains blocked as normal.
This is the way.
Vastly superior to local dns.
This is specifically info about LetsEncrypt, not general SSL.
Yes my answer is for use with Let’s Encrypt.
I don’t really understand what you’re getting at. The answer to OPs question is to use letsencrypt like everyone else.
They literally didn’t mention LE at all.
SSL is not LetsEncrypt, if you didn’t know.
To add: a lot of cert providers also offer ACME so while the primary user of ACME is LetsEncrypt, you can use the same tech and validations as LetsEncrypt on other vendors too.
deleted by creator
You need a DNS service that works with Let’s encrypt
NPM is in my post…
I don’t get it. Npm is a package manager. It doesn’t handle certificates.
You need a DNS service like route 53 (AWS) or similar where let’s encrypt connects via an API and creates the DNS token.
OP isn’t referring to the package manager. They’re talking about Nginx Proxy Manager
Oh
That makes sense. We need to stop making two things use the same acronym. Its like people saying HA for home assistant without realizing that HA is normally used for high availability.
Then you’re all set, issue certs over DNS-01 challenge in NPM, and create records in your local DNS server that point to the NPM IP for each domain you want to use.
OP is asking for cases where you don’t want to allow the service (or reverse proxy) to be accessible via the web.
As I understand it, OP just wants to hide (=remove) the subdomains from the public URLs.
They do not. See my other reply about DNS verification.
Your response clearly states publicly accessible DNS. A CA does not require anything public for local SSL and can work in conjunction with whatever service they want for that which is public.
Fair, I don’t know why I read OPs post as asking for let’s encrypt certs. Internal CA is indeed an option.
I do exactly this with traefik.
I followed this guide: https://youtu.be/liV3c9m_OX8
I recommend this one instead: https://youtu.be/n1vOfdz5Nm8
Same guy, just fresh version of Traefik 😁
deleted by creator
If you have wildcard certs, you just install them everywhere your services are running.
As far as redirects go, you just 302 redirect from one host to another.
Unless you’re asking about resolving hosts on your internal network and public ones differently, which is a lot more complicated than you probably want to deal with if you’re already kind of lost. Just setup a VPN to your internal network and be done with it. Otherwise setup a local DNS resolver to bridge your public DNS and local requests.
