search

OpenMediaVault-Plugin-Developers / openmediavault-letsencrypt

Plugin for generating letsencrypt.org certificates for Open Media Vault
16 stars 8 forks source link

how to change challange to DNS ? #9

Open mulera84 opened 6 years ago

mulera84 commented 6 years ago

Hi, I wander if you can add the ability to make challenge by dns some ISPs disable the port 80 toward clients i know that is build in already and can be done with this command (for he.net dynamic server ) acme.sh --issue --dns dns_he -d mydomain.com

ryecoaaron commented 6 years ago

Two things... the plugin uses certbot not acme.sh and that method can’t use automatic renewal

mulera84 commented 6 years ago

Hi thanks @ryecoaaron I found this AddOn that will allow dns over certbot https://github.com/angel333/certbot-he-hook can it be combined to the automation made by your plugin?

hans00 commented 6 years ago

I forked this plugin and modify it I am use acme.sh https://github.com/hans00/openmediavault-acme

ryecoaaron commented 6 years ago

Looks decent although I would remove the files in migrations.d (it won't upgrade the letsencrypt plugin since it is named different) and I wouldn't store the acme.sh file in /root/. Put it in /usr/local/sbin or something.

KarstenDE commented 3 years ago

I would highly appriciate such a solution. Ususally I don't want to publish my NAS to the internet just to get a valid TLS-Certificate for the admin interface.

Other solutions use it via DNS-Challenge which works super easy with an own domain e.g. configured at cloudflare DNS: https://pve.proxmox.com/wiki/Certificate_Management#sysadmin_certs_acme_dns_challenge