Home / Acmefyer / Internal servers
Let’s Encrypt for internal servers, without port 80.
Intranet, file server interface, printer portal, management console: internal services need valid certificates just as much, but cannot be reached from the internet. Acmefyer obtains the certificates through DNS validation, without any internal server opening a port to the outside, and an agent installs them where they are needed.
Why HTTP-01 does not work for internal servers.
With the usual HTTP-01 validation, Let’s Encrypt fetches a file under /.well-known/acme-challenge/ on port 80, from the internet. An internal server cannot be reached there, and nobody wants to open a port just for validation.
With DNS-01 you prove control of the domain with a TXT record in the public DNS zone instead, for example:
_acme-challenge.intranet.example.com. 300 IN TXT "gfj9Xq...Rg85nM"
The server itself takes no part in the validation. It only needs a public name under your domain. Whether that name points to an address on the internet does not matter.
- HTTP-01
- Port 80 must be reachable from the internet, without a broken redirect.
- DNS-01
- A TXT record _acme-challenge in the public zone. No server has to be reachable from the outside.
- Internal names
- Public certificate authorities do not issue names such as server.company.local or private IP addresses. The usual way is a name under your own domain, such as intranet.example.com. For purely internal names, Acmefyer’s local CA issues the certificate.
- Split-DNS
- If your own DNS server answers the zone differently from the internet, typically with Active Directory, only what the internet sees counts for validation.
Only the Acmefyer server talks to the internet.
The Acmefyer server orders the certificate from Let’s Encrypt or another ACME certificate authority, creates the validation record through your DNS provider’s API, waits until public DNS servers see it and removes it afterwards. It renews the certificate on its own 30 days before expiry.
The Acmefyer agent runs on the internal servers. It connects outbound to the Acmefyer server only, picks up the certificate and installs it locally. The internal servers need neither an open port nor internet access for this.
- Acmefyer server
- Outbound to the certificate authority, to the DNS provider and to www.wedigo.net for the license, also through a proxy.
- Agents
- Outbound to the Acmefyer server only, via HTTPS with mutual certificate verification (mTLS).
- DNS providers
- Around 190, including Cloudflare, Hetzner, IONOS, INWX, Azure DNS and Amazon Route 53, plus your own DNS servers via RFC 2136.
- Public view
- Acmefyer asks public DNS servers such as Cloudflare or Quad9 whether the validation record is visible, not the internal DNS. The selection is configurable.
- Credentials
- DNS provider API tokens are stored encrypted with AES-256-GCM in the embedded database.
- Targets
- For example IIS, Exchange, the Windows certificate store, NGINX, Apache, Traefik, HAProxy, Tomcat or your own scripts.
- 01
Choose a name
For example intranet.example.com. Internally your DNS server points to the server as before.
- 02
DNS access
Store your DNS provider’s API token, once per account or project.
- 03
Add a domain
With Let’s Encrypt and validation via DNS-01.
- 04
Install the agent
On the internal server. It detects the applications serving TLS, and one click creates the deployment.
