# VaulTLS

VaulTLS is a self-hosted web application that centralizes mutual TLS certificate management for home labs, allowing users to create, distribute, and track expirations with optional OpenID Connect login and Automated. It is open source and self-hosted, installable on Unraid.

Canonical page: https://ourlocalhost.com/app/3441/vaultls

## Description

VaulTLS is a self-hosted web application that centralizes mutual TLS certificate management for home labs, allowing users to create, distribute, and track expirations with optional OpenID Connect login and Automated Certificate Management Environment (ACME) certificate-authority support.

## Platform availability

Available on 2 of 10 platforms: Unraid, Any server.

## Health score

67/100 (Good), based on 5 of 5 factors.
- Maintained: 100 (last commit 25 days ago)
- Popular: 62 (1,199 GitHub stars)
- Easy to install: 45 (2 install platforms, install notes, Docker image)
- Light to run: 10 (8 GB minimum RAM)
- Security check: 70 (no serious findings, 5 minor, CI, tests)

## Links

- Unraid: https://ca.unraid.net/apps/vaultls-0is9uxz0ah2dn7?q=VaulTLS
- GitHub: https://github.com/7ritn/VaulTLS

## Common questions

### Why can't I log in to VaulTLS over HTTP?

Access VaulTLS over HTTPS, because it expects a secure connection. If insecure access is needed, set VAULTLS_INSECURE=true.

### Does VaulTLS support OIDC login or ACME certificate issuance?

Yes, it has optional OIDC login and ACME CA support for Traefik and acme.sh.

### Should VaulTLS be exposed directly or put behind a reverse proxy?

It is recommended to run it behind a reverse proxy for TLS termination.

### What Docker issue has been reported with VaulTLS 0.9.1?

A user reported high CPU in /usr/bin/backend and the app returning to the initial setup page after about half an hour.

---
Source: Our Local Host (https://ourlocalhost.com/app/3441/vaultls), the self-hosted and open-source app directory.
