Bug #11783
closed
/usr/local/pkg/acme/acme_command.sh : Uncaught RuntimeException: Couldn't create directory
0%
Description
Tried to setup acme on new firewall instance using old Key & ID from previous installation
Failed to write directory for some reason, unclear if this is related to the script or some other process issue.
Version 2.5.0-RELEASE (amd64)
built on Tue Feb 16 08:56:29 EST 2021
FreeBSD 12.2-STABLE
VMware Virtual Machine
Netgate Device ID: e33bffd2b91a14f384c8
BIOS Vendor: Phoenix Technologies LTD
Version: 6.00
Release Date: Tue Jul 30 2013
CPU Type Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
4 CPUs: 1 package(s) x 4 core(s)
AES-NI CPU Crypto: Yes (active)
Hardware crypto AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS
====================
Crash report begins. Anonymous machine information:
amd64
12.2-STABLE
FreeBSD 12.2-STABLE d48fb226319(devel-12) pfSense
Crash report details:
PHP Errors:
[05-Apr-2021 20:04:12 Australia/Brisbane] PHP Fatal error: Uncaught RuntimeException: Couldn't create directory: '' to expose challenge for certificate: firewall.13contXXXXXXXXXXXXX. in /usr/local/pkg/acme/acme.inc:1613
Stack trace:
#0 /usr/local/pkg/acme/acme_command.sh(89): pfsense_pkg\acme\challenge_response_put('firewall.13cont...', 'firewall.13cont...', 'cQMN4-5f3WbYxEG...', 'cQMN4-5f3WbYxEG...')
#1 {main}
thrown in /usr/local/pkg/acme/acme.inc on line 1613
No FreeBSD crash data found.
Updated by Martin Thygesen about 3 years ago
user was admin during setup process so permissions to create a director should not have been an issue.
Updated by Jim Pingle about 3 years ago
- Status changed from New to Not a Bug
Looks like a settings issue, it's got an entry set to need a web root folder but the value is empty.