Git Product home page Git Product logo

acme-esxi's Introduction

Originally a product of w2c/letsencrypt-esxi. Modified for those of us that are either unable or unwilling to expose our ESXi management interfaces to the Internet.

Let's Encrypt for VMware ESXi

acme-esxi is a lightweight open-source solution to automatically obtain and renew Let's Encrypt or private ACME CA certificates on standalone VMware ESXi servers. Packaged as a VIB archive or Offline Bundle, install/upgrade/removal is possible directly via the web UI or, alternatively, with just a few SSH commands.

Features:

  • Fully-automated: Requesting and renewing certificates without user interaction
  • Auto-renewal: A cronjob runs once a week to check if a certificate is due for renewal
  • Persistent: The certificate, private key and all settings are preserved over ESXi upgrades
  • Configurable: Customizable parameters for renewal interval, Let's Encrypt (ACME) backend, etc
  • Can be used with any ACME CA: LabCA is a great example.

Successfully tested with all currently supported versions of ESXi (6.5, 6.7, 7.0).

Troubleshooting

See the Wiki for possible pitfalls and solutions.

License

acme-esxi is free software;
you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation,
either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <http://www.gnu.org/licenses/>.

acme-esxi's People

Contributors

churro avatar

Stargazers

 avatar  avatar  avatar

Forkers

tualua

acme-esxi's Issues

400: Connection reset by peer

Interestingly, even a newly installed ESXi instance on 7.0U3 when handed the proper certificates, causes a 400 Connection Reset By Peer when my LabCA instance tries to query it. I thought I had this working, but apparently this has only worked once, and I haven't been able to replicate what I even did to make it work.

The default Let's Encrypt functionality remains functional as it is otherwise unchanged by default from the original project.

Going to open this issue for myself to work on this more.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.