I'am using nginx proxy manger to get the certificates, and that works well.
Cause de subdomains are public, they are exposed.
Is there a way to get one cert for the domain, witch i can use internaly for the subdomains?
In other words, i want to hide the subdomains.
To hide subdomains the option would be to use a wildcard certificate. But that would require the dns-01 challenge, which is often/sometimes more difficult to implement. And as you're using nginx proxy manager, you're pretty much on your own figuring that out. That's because NPM isn't a very popular software application to debug here on this Community and I'm not familiar with any volunteer having much experience with it.
No it is not the right domain, just an example of it.
Bottom line is, that i want the subdomains not be exposed.
VIa NPM i get certs for all the domains. I've red some about wildcards, but i think i 'am to inexpierenced to implement that.
I need to make local domains as i now do at the hosting provider.
This is not a common ground for me.
Please refrain from using real world domain names as examples. Please remove the currently used real world domain name and change to e.g. example.com, one of the IANA domain names reserved specially for thus purpose.
Can you clarify what you mean by "exposed"? If the server is just to be used on some internal network, then you can use the DNS-01 challenge (as previously stated, required for wildcards but can be used for non-wildcard names too), though the name would still be public. Or, you can try to configure some sort of firewalling that allows Let's Encrypt's validation servers through (by only opening when attempting renewal, or by allowing all requests for .well-known/acme-challenge) but blocks whatever you don't want to "expose".
I have a homelab, where i host a application that is calles ejabberd.
Ejabberd is a xmpp server. xmpp is a protocol that is also used by Whatsapp.
The server needs 5 subdomains.
I have a domain example.com and on the hoster i have 5 subdomains
With A and SRV records on the userpanel of the hoster, i have forward the services to my ipadress at home. Via NPM on port 80, i can get Letsencrypt certs.
What i try to accomplish, is that i want that my server can handle the subdomains.
For what i know i must use wildcards.
I don't want that those domains are visible by using dnsdumpster.
So, to answer Peter's question then ... You don't need to access the subdomain services from the public internet then? Because their IP will have to be in the public DNS to clients can find the IP. Or, use a DNS wildcard so any subdomain name resolves to the same IP.
Let's Encrypt is a public Certificate Authority (CA) so only issues certs for domain names in the public DNS. You can get a wildcard cert with just the base domain name and any subdomain. But, as noted that requires a DNS Challenge. Otherwise each name must have a public A and/or AAAA record so Let's Encrypt (or anyone) can locate the IP to connect to that domain
Maybe, maybe not. We have seen numerous blogs and videos suggested by visitors here that had very poor instructions. Even some that were ridiculously wrong.
Maybe your video is fine. But without some expert review it's hard to know. I have often read blogs and such for review but a 25min video - forget it. I am a fast reader but not a fast watcher
The simple answer is if you don't want your subdomain name known in the public DNS or the public Certificate Transparancy (CT) logs you have to use a wildcard cert. And, for that Let's Encrypt requires the DNS Challenge.
LE provides below which is sometimes helpful in a similar situation