Displaying 1 to 20 from 21 results

acme - :lock: acmetool, an automatic certificate acquisition tool for ACME (Let's Encrypt)

  •    Go

acmetool is an easy-to-use command line tool for automatically acquiring certificates from ACME servers (such as Let's Encrypt). Designed to flexibly integrate into your webserver setup to enable automatic verification. Unlike the official Let's Encrypt client, this doesn't modify your web server configuration.You can perform verifications using port 80 or 443 (if you don't yet have a server running on one of them); via webroot; by configuring your webserver to proxy requests for /.well-known/acme-challenge/ to a special port (402) which acmetool can listen on; or by configuring your webserver not to listen on port 80, and instead running acmetool's built in HTTPS redirector (and challenge responder) on port 80. This is useful if all you want to do with port 80 is redirect people to port 443.

dehydrated - letsencrypt/acme client implemented as a shell-script – just add water

  •    Shell

It uses the openssl utility for everything related to actually handling keys and certificates, so you need to have that installed. Please keep in mind that this software and even the acme-protocol are relatively young and may still have some unresolved issues. Feel free to report any issues you find with this script or contribute by submitting a pull request.

acme.sh - A pure Unix shell script implementing ACME client protocol

  •    Shell

It's probably the easiest & smartest shell script to automatically issue & renew the free certificates from Let's Encrypt.

certbot - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server

  •    Python

Certbot is part of EFF’s effort to encrypt the entire Internet. Secure communication over the Web relies on HTTPS, which requires the use of a digital certificate that lets browsers verify the identity of web servers (e.g., is that really google.com?). Web servers obtain their certificates from trusted third parties called certificate authorities (CAs). Certbot is an easy-to-use client that fetches a certificate from Let’s Encrypt—an open certificate authority launched by the EFF, Mozilla, and others—and deploys it to a web server. Anyone who has gone through the trouble of setting up a secure website knows what a hassle getting and maintaining a certificate is. Certbot and Let’s Encrypt can automate away the pain and let you turn on and manage HTTPS with simple commands. Using Certbot and Let's Encrypt is free, so there’s no need to arrange payment.

certmagic - Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal

  •    Go

CertMagic is the most mature, robust, and capable ACME client integration for Go. With CertMagic, you can add one line to your Go application to serve securely over TLS, without ever having to touch certificates.

acme-client - Let's Encrypt / ACME client written in PHP for the CLI.

  •    PHP

kelunik/acme-client is an ACME client written in PHP. ACME is the protocol that powers the Let's Encrypt certificate authority.

freshcerts - ACME certificate protocol (Let's Encrypt) proxy client with a dashboard and monitoring

  •    Ruby

ACME (currently implemented by Let's Encrypt) is a way to automatically (re)issue TLS certificates. freshcerts solves both problems. It runs a server that exposes a much simpler API to your servers (they'll use a tiny shell script that's pretty much openssl | curl | tar) and a dashboard to your system administrators. Servers are monitored to ensure they actually use the certs issued for them. Email notifications are sent to the admins for all errors found by monitoring and for all issued certificates.

certificaat - General-purpose ACME client

  •    Clojure

Certificaat is a general-purpose ACME client, fully compatible with the Let’s Encrypt CA. Certificaat’s aim is to help you retrieve a certificate for your domain, and subsequently help you set up a cron job and forget about it.

chef-acme - Chef cookbook to request SSL certificates at Let's Encrypt

  •    Ruby

Automatically get/renew free and trusted certificates from Let's Encrypt (letsencrypt.org). ACME is the Automated Certificate Management Environment protocol used by Let's Encrypt. Installs the required acme-client rubygem.

acmesmith - An effective ACME client: Manage keys on the cloud (e.g. S3)

  •    Ruby

Acmesmith is an ACME (Automatic Certificate Management Environment) client that works perfect on environment with multiple servers. This client saves certificate and keys on cloud services (e.g. AWS S3) securely, then allow to deploy issued certificates onto your servers smoothly. This works well on Let's encrypt. This tool is written in Ruby, but Acmesmith saves certificates in simple scheme, so you can fetch certificate by your own simple scripts.


  •    Shell

It will manage all routes with (by default) butter.sh/letsencrypt-managed=yes labels in the project/namespace, it's deployed in. For now, there are the following limitations.

Posh-ACME - ACMEv2 protocol client for generating certificates using Let's Encrypt (or other ACMEv2 compliant CA)

  •    PowerShell

An ACME v2 client implemented as a Windows PowerShell module that enables you to generate publicly trusted SSL/TLS certificates from an ACME capable certificate authority such as Let's Encrypt. The latest release version can found in the PowerShell Gallery. Installing from the gallery requires the PowerShellGet module which is installed by default on Windows 10 or later and all versions of PowerShell Core. See Getting Started with the Gallery for instructions on earlier OSes. Zip/Tar versions can also be downloaded from the GitHub releases page.

acme - Acme (Let's Encrypt) Client for Elixir

  •    Elixir

All client request are called with a connection. I chose to do it this way (over something like hard coded config) so you have the flexability to run multiple connections to many Acme servers at the same time or fetch certificates for different accounts.

openshift-acme - ACME Controller for OpenShift and Kubernetes Cluster. (Supports e.g. Let's Encrypt)

  •    Go

openshift-acme is ACME Controller for OpenShift and Kubernetes clusters. It will automatically provision certficates using ACME protocol and manage their lifecycle (like automatic renewals). Let's encrypt provides two APIs: live and staging. There is also an option to deploy the controller to watch the whole cluster or only single namespace depending on what privileges you have.

letsdebug - Diagnostic tool/website to help figure out why you can't issue a certificate for Let's Encrypt

  •    Go

Let's Debug is a diagnostic website, API, CLI and Go package for quickly and accurately finding and reporting issues for any domain that may prevent issuance of a Let's Encrypt SSL certificate for any ACME validation method. It is motivated by this community thread.

sewer - Let's Encrypt(ACME) client. CLI app & python library

  •    Python

Sewer is a Let's Encrypt(ACME) client. It's name is derived from Kenyan hip hop artiste, Kitu Sewer. It allows you to obtain ssl/tls certificates from Let's Encrypt. Sewer also ships with a commandline interface(called sewer or sewer-cli) that you can use to get/renew certificates. Your dns providers credentials need to be supplied as environment variables.

acme - Async ACME library written in PHP based on the Amp concurrency framework.

  •    PHP

kelunik/acme is a non-blocking implementation of the ACME protocol based on the amp concurrency framework. If you're looking for a PHP client, have a look at kelunik/acme-client which is based on this library.

terraform-provider-acme - ACME (Let's Encrypt) Support for Terraform

  •    Go

This is the repository for the Terraform ACME Provider, which one can use with Terraform to manage and generate certificates generated by an ACME CA, such as Let's Encrypt. For general information about Terraform, visit the official website and the GitHub project page.