[wp-meta] [Making WordPress.org] #5492: Rosetta: Expired SSL certificate error when building WordPress packages manually
Making WordPress.org
noreply at wordpress.org
Thu Oct 29 22:47:55 UTC 2020
#5492: Rosetta: Expired SSL certificate error when building WordPress packages
manually
-------------------------------------------+--------------------
Reporter: SergeyBiryukov | Owner: (none)
Type: defect | Status: new
Priority: normal | Milestone:
Component: International Sites (Rosetta) | Keywords:
-------------------------------------------+--------------------
Reported by @fierevere in
[https://wordpress.slack.com/archives/C02RQBWTW/p1604004109471600 #core on
Slack].
When using the Build New Package form on Rosetta sites, there is now an
error displayed:
`svn: E170013: Unable to connect to a repository at URL
'https://svn.automattic.com/wordpress-i18n/ru_RU/branches/3.7' svn:
E230001: Server SSL certificate verification failed: certificate has
expired`
The certificate appears to have expired on October 8th:
{{{
Subject: *.automattic.com
Altnames: DNS:*.automattic.com, DNS:automattic.com
Issuer: Go Daddy Secure Certificate Authority - G2
Not valid before: Aug 31 13:18:13 2018 GMT
Not valid after: Oct 8 13:02:24 2020 GMT
}}}
I guess the repo URLs in the builder tool should be updated to the
canonical https://i18n.svn.wordpress.org/ URL.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5492>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list