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

[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 (19.44 KiB) Viewed 10059 times

[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

[mampsupportmod]

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.

[Radjin]

I have found in MAMP 7.1.3 I can give read/write permissions to me for the Live and Archive directories, and MAMP can read and save the cert and privkey, but not the chain, all from the live folder. When I test the cert, it says it issued from E5, not from MAMP but without the chain file it still shows up as not trusted in https://www.sslshopper.com/ssl-checker.html.

[Radjin]

Not sure what I did different but it's fixed. I looked up and modified the template http-ssl.conf to look for the .pem files, saved and the server would not start with a config error. So I commented out my changes and uncommented the original MAMP lines. Upon restart it worked.