Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

after succesful dry run error with path #2

Open
PeterWagemans opened this issue Jul 24, 2024 · 0 comments
Open

after succesful dry run error with path #2

PeterWagemans opened this issue Jul 24, 2024 · 0 comments

Comments

@PeterWagemans
Copy link

Hi Wim,

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant