mirror update-center.json can't identify LTS update about update-center-mirror HOT 8 CLOSED

Thanks for your bug report.

from update-center-mirror.

I fixed this issue. You can use a new address which is https://updates.jenkins-zh.cn/update-center.json.
If you want to know more tech details, please feel free to visit here.

from update-center-mirror.

Another error info, i do check update after i update the https://updates.jenkins-zh.cn/update-center.json.
update center: Signature verification failed in update site 'default' （显示详情）

java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors
	at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:153)
	at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79)
	at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292)
	at org.jvnet.hudson.crypto.CertificateUtil.validatePath(CertificateUtil.java:93)
	at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:88)
	at hudson.model.UpdateSite.verifySignature(UpdateSite.java:254)
	at hudson.model.UpdateSite.updateData(UpdateSite.java:218)
	at

from update-center-mirror.

What's the version of your Jenkins?

from update-center-mirror.

Jenkins ver. 2.190.1

from update-center-mirror.

I just tested it in a new environment with 2.190.1. It's ok. Please make sure that you follow the right flow:

• use the new certificate
• change to the new update center site.

from update-center-mirror.

I also encountered the same problem mentioned above. What does "use the new certificate" mean? what should I do?

from update-center-mirror.

You should put this file into your Jenkins. I believe that you can get more details from here.

from update-center-mirror.