You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tested this on my Mac, and somewhat later on Ubuntu 22 running on the pi4b here.
peter@fms:/opt/FileMaker/FileMaker Server/Tools/Lets_Encrypt$ sudo ./fms-request-cert-dns-route53.sh
[WARNING]: /opt/FileMaker/FileMaker Server/CStore/Certbot not found. Creating necessary directories.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Generating test certificate request.
Saving debug log to /opt/FileMaker/FileMaker Server/CStore/Certbot/letsencrypt.log
Account registered.
Simulating a certificate request for fms.clarify.net
The dry run was successful.
realpath: '/opt/FileMaker/FileMaker Server/CStore/Certbot/live/fms.clarify.net/privkey.pem': No such file or directory
Private key:
realpath: '/opt/FileMaker/FileMaker Server/CStore/Certbot/live/fms.clarify.net/fullchain.pem': No such file or directory
Certificate:
[ERROR]: An error occurred with certificate generation. No private key found at
On both platforms the same error and indeed the directory does not exist at that moment. It is created when not doing a dry run.
Maybe to the exit (currently in line 215) a bit earlier?
The text was updated successfully, but these errors were encountered:
Hi Wim,
Tested this on my Mac, and somewhat later on Ubuntu 22 running on the pi4b here.
On both platforms the same error and indeed the directory does not exist at that moment. It is created when not doing a dry run.
Maybe to the exit (currently in line 215) a bit earlier?
The text was updated successfully, but these errors were encountered: