Page 1 of 1

Let's Encrypt private keys issued with no "read access" for MAMP Pro?

Posted: Tue Jan 26, 2021 12:30 pm
by mampsupportmod
I have to give my Mac user account read access to Let's Encrypt's privkey.pem otherwise MAMP cannot load the SSL file as part of the chain. These certificates issued before would automatically give the Mac user account read access but not anymore. Going into each privkey to set permissions is annoying after a renewal period. Anyone else having this issue?

Lets Encrypt Priv Key No Access
Lets Encrypt Priv Key No Access (19.44 KiB) Viewed 6774 times

Re: Let's Encrypt private keys issued with no "read access" for MAMP Pro?

Posted: Sat May 22, 2021 11:18 am
by keith
I'm on a Mac and I've recently set up a website with Mamp Pro using a Let's Encrypt certificate. It works fine currently, but from what you say when the certificate is renewed I will need to give the privacy.pem file access for my user account after each renewal.

I wonder did you manage to get this resolved yet? I'd be grateful for any advice so I can avoid it when it happens.

Thanks in advance,
Keith

Re: Let's Encrypt private keys issued with no "read access" for MAMP Pro?

Posted: Wed Jun 30, 2021 3:49 pm
by mampsupportmod
keith wrote: Sat May 22, 2021 11:18 am I'm on a Mac and I've recently set up a website with Mamp Pro using a Let's Encrypt certificate. It works fine currently, but from what you say when the certificate is renewed I will need to give the privacy.pem file access for my user account after each renewal.

I wonder did you manage to get this resolved yet? I'd be grateful for any advice so I can avoid it when it happens.

Thanks in advance,
Keith
I haven't. privkey.pem keys issued by certbot still appear to be unreadable by MAMP Pro. You will need to manually adjust the key's permissions in order to apply and save your key to a MAMP host. According to Let's Encrypt, the keys are being issued with the correct permissions.