I’m attempting to remove a site from DevKinsta, but it’s stuck at Removing SSL Certificate.
This is what I found in the log file:
2022-06-10 08:12:02.286] [error] [ipcMainStep] Error in operation DELETE_SITE, step removeCertification: Error: Encountered an error: Error: Command failed: security delete-certificate -c captaincaliente.local -t
security: SecKeychainItemDelete: Write permissions error.
Any help on what to do next would great. Thanks! (Also let me know if more of the log file is needed.)
Hi @emcaleb, welcome to DevKinsta!
So this seems specific to your Mac. Can you try creating a blank site just to see if you run into an error when DevKinsta tries to create the SSL certificate? If not, are you then able to delete the new site without this error?
I believe you can also try manually deleting the ssl certificate by running that command from your terminal:
security delete-certificate -c captaincaliente.local -t
I am having the same issue:
[2022-06-23 17:36:08.738] [error] [ipcMainStep] Error in operation DELETE_SITE, step removeCertification: Error: Encountered an error: Error: Command failed: security delete-certificate -c wpcreative.local -t
security: "wpcreative.local" is ambiguous, matches more than one certificate
I haven’t spent the time to figure this one out yet, but I did find this: https://stackoverflow.com/questions/39868578/security-codesign-in-sierra-keychain-ignores-access-control-settings-and-ui-p
I think because I’ve upgraded operating systems since this site was developed locally, there’s a keychain conflict. That’s just my theory so far though.
To add to @emcaleb’s theory, @wpcreative-jw, I think your error is slightly different. It’s saying you have multiple certificates with the same name so DevKinsta can’t delete the certificate it added with that command. This might be helpful: macos - Example for Mac OS X security delete-certificate -c <name>? - Stack Overflow
My only guess is that either DevKinsta created two certificates with the same name or a different app created the other certificate(s).
I’ll also ask our developers for advice here to see if there’s another way around this. I don’t think we’ve seen either error before so we’ll have to see if there’s a better way to handle this step.