Privkey.pem is empty after generating a new certificate

Never mind- found the permissions error.

My domain is: ftp.nyc.arcadeedit.com

I ran this command:
files:renewal actualize1$ sudo certbot certonly
Saving debug log to /var/log/letsencrypt/letsencrypt.log

How would you like to authenticate with the ACME CA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Apache Web Server plugin (apache)
2: Spin up a temporary webserver (standalone)
3: Place files in webroot directory (webroot)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-3] then [enter] (press 'c' to cancel): 3
Plugins selected: Authenticator webroot, Installer None
Please enter in your domain name(s) (comma and/or space separated)  (Enter 'c'
to cancel): ftp.nyc.arcadeedit.com
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for ftp.nyc.arcadeedit.com
Input the webroot for ftp.nyc.arcadeedit.com: (Enter 'c' to cancel): /usr/local/Rumpus/
Waiting for verification...
Cleaning up challenges


IMPORTANT NOTES:

 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/ftp.nyc.arcadeedit.com/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/ftp.nyc.arcadeedit.com/privkey.pem
   Your cert will expire on 2019-04-08.}

My web server is (include version): Rumpus
The operating system my web server runs on is (include version): Mac OSX 10.12.6
I can login to a root shell on my machine (yes or no, or I don’t know): Yes

When I look inside the fullchain.pem I see all the expected text, but privkey.pem-while created-is showing as an empty file. The above was the second attempt at creating the certificate. Both times, nothing in privkey.pem.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.