Approximate time to read: 2 minutes
I’ve been using svnX for years now for managing my WordPress plugins with the svn repositories that WordPress.org provide. It’s pretty old-school and I keep intending to move to Versions but, yeah, time always seems to be against me.
However, I’ve now started getting the following errors against all my repos…
svn: E230001: Server SSL certificate verification failed: issuer is not trusted
svnX doesn’t give me any opportunity to do anything with this so I’m unable to access my repos as a result.
I’ve engaged with the WordPress.org plugins team to see if they know what the issuew with the certs may be but, until then a temporary fix, as it turns out, is pretty simple. svnX is, behind the scenes, using svn, which you can access from the command line.
So, kick open a Terminal window and run the following command…
svn list [repository URL]
Where you replace [repository URL] with the appropriate URL of your repository. It will then prompt you to reject or accept the certificate (either permanently or temporarily). Once that’s done, you can then access the repo again via svnX. Here’s what it looks like when I did it for one of my plugin repositories…
svn list https://plugins.svn.wordpress.org/no-self-ping Error validating server certificate for 'https://plugins.svn.wordpress.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: *.svn.wordpress.org - Valid: from Jun 20 19:25:08 2018 GMT until Jul 15 19:04:26 2020 GMT - Issuer: Go Daddy Secure Certificate Authority - G2, http://certs.godaddy.com/repository/, GoDaddy.com, Inc., Scottsdale, Arizona, US - Fingerprint: [redacted] (R)eject, accept (t)emporarily or accept (p)ermanently? p
Because the cert, in this case, covers all of the wp.org repo, just running this once is sufficient to then correct for all the repositories that you may have there.