Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

nager/Nager.CertificateManagement

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

68 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Caution

The project no longer works in its current state. As I no longer need it, it will be archived.

Nager.CertificateManagement

Nager.CertificateManagement provides Lets Encrypt certificates for internal servers, switches, etc. or developers. The certificates are requested via the DNS challenge, so that the internal devices do not need an external connection and you must not share your DNS Management credentials with everyone. The certificates can be requested via a web interface and are available for download there after generation. Standard certificates and wildcard certificates can be requested. The docker container is available via dockerhub.

Management Portal

Nager.CertificateManagement

Architecture Overview

Nager.CertificateManagement
The certificates can then be obtained by the individual servers from the S3 storage. In contrast to other solutions, the access data for the servers does not have to be stored at a central location. S3 policies can also ensure that each system can only query its certificate.

Supported DNS Provider

Start Application

Update the configuration in the docker-compose.yml file before start the application. After the start the application is available under http://localhost

LETSENCRYPT__EMAIL: your@email.com
LETSENCRYPT__REQUESTMODE: TEST OR PRODUCTION
DNSPROVIDER__HETZNER__APIKEY: APIKEY OF THE PROVIDER (OPTIONAL)
DNSPROVIDER__CLOUDFLARE__APIKEY: APIKEY OF THE PROVIDER (OPTIONAL)
docker-compose up

Update application

docker-compose pull

Alternative and interesting projects on this topic

Language Project
Python lexicon
.NET certify
GO lego
PowerShell Posh-ACME
Phyton Netflix Lemur