From 27d89b85955cf1cc7cd3bd721ff3fbdff062fa0d Mon Sep 17 00:00:00 2001 From: Franco Fichtner Date: Tue, 6 Sep 2022 08:59:35 +0200 Subject: [PATCH] security/acme-client: "move" to NAME_setup use setup.sh is being used much more differently here than anywhere else. Not touching any of the integration, but the general problem might be that it tries to do something else entirely that doesn't fit any other plugin paradigm and might break at a later point. PR: https://github.com/opnsense/core/issues/5917 --- .../opnsense/service/templates/OPNsense/AcmeClient/rc.conf.d | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/security/acme-client/src/opnsense/service/templates/OPNsense/AcmeClient/rc.conf.d b/security/acme-client/src/opnsense/service/templates/OPNsense/AcmeClient/rc.conf.d index b43c75151..96d20f1bc 100644 --- a/security/acme-client/src/opnsense/service/templates/OPNsense/AcmeClient/rc.conf.d +++ b/security/acme-client/src/opnsense/service/templates/OPNsense/AcmeClient/rc.conf.d @@ -2,7 +2,7 @@ acme_http_challenge_enable=YES acme_http_challenge_conf="/var/etc/lighttpd-acme-challenge.conf" acme_http_challenge_pidfile="/var/run/lighttpd-acme-challenge.pid" -acme_http_challenge_var_script="/usr/local/opnsense/scripts/OPNsense/AcmeClient/setup.sh" +acme_http_challenge_setup="/usr/local/opnsense/scripts/OPNsense/AcmeClient/setup.sh" {% else %} acme_http_challenge_enable=NO {% endif %}