<p>Following your comment confirming you can use your own signed certificates internally.</p>

<p>One solution would be to replace the current certificate on your repo with a new one holding <code>updates.jenkins-ci.org</code> as an alias. <a href="https://stackoverflow.com/questions/10175812/how-to-create-a-self-signed-certificate-with-openssl/27931596#27931596">This response on stackoverflow</a> has the necessary info to get you going.</p>

<p>Meanwhile, the <a href="https://wiki.jenkins.io/display/JENKINS/UpdateSites+Manager+plugin" rel="nofollow noreferrer">plugin higlighted above by @casey vega in the comments</a> (which I didn't know) seems to be a solution much easier to manage.</p>

CC BY-SA 4.0
2019-05-28T21:39:19.423Z
2019-05-28T21:39:19.423Z
Zeitounator
<p>Is there a way that I can tell Jenkins to ignore certificates for the update site. </p>

<p><strong>Background</strong></p>

<p>I have an air-gapped Jenkins installation and there is currently <a href="https://stackoverflow.com/questions/54548140/jenkins-plugin-repo-as-proxy-repo-when-behind-a-firewall/56321607#56321607">proper way to make a proxy repo</a>. Thus I have the following setup:
- I have modified the <code>hosts</code> file on the Jenkins host so that <code>updates.jenkins-ci.org</code> points to the host of the internal artifact repo
- There is a reverse-proxy in front of artifact repo which handles traffic for <code>updates.jenkins-ci.org</code></p>

<p>However we are only allowed to use https thus there will be a <code>name mismatch error</code> as the certificate does not match the hostname of the artifact repo host</p>

<p>Remark: I don't want to generally disable the checks but only for the update site so the <code>The Skip Certificate Check plugin</code> is not the solution for me</p>

CC BY-SA 4.0
2019-05-27T18:54:37.250Z
I don't think it is possible. Can you consider using certs signed by your own created CA, either on the artifact repo host or on a specific reverse proxy you control ?
Zeitounator
CC BY-SA 4.0
2019-05-28T17:22:40.737Z
Well I obviously can use self-signed certificates, but the problem is the host-name missmatch as the hostname of my repo server or reverse proxy is not `updates.jenkins-ci.org`
papanito
CC BY-SA 4.0
2019-05-28T19:55:26.607Z
I would take a look at the following project and plugin:

https://github.com/jenkinsci/juseppe
https://wiki.jenkins.io/display/JENKINS/UpdateSites+Manager+plugin
casey vega
CC BY-SA 4.0
2019-06-02T09:17:21.170Z
Thanks @casey vega didn't knew about this
papanito
<jenkins>
Jenkins plugin site to ignore certificates
papanito
# Jenkins plugin site to ignore certificates

(Asked by: username_0 on 2019-05-27)

Is there a way that I can tell Jenkins to ignore certificates for the update site.

**Background**

I have an air-gapped Jenkins installation and there is currently [proper way to make a proxy repo](https://stackoverflow.com/questions/54548140/jenkins-plugin-repo-as-proxy-repo-when-behind-a-firewall/56321607#56321607). Thus I have the following setup:
- I have modified the `hosts` file on the Jenkins host so that `updates.jenkins-ci.org` points to the host of the internal artifact repo
- There is a reverse-proxy in front of artifact repo which handles traffic for `updates.jenkins-ci.org`

However we are only allowed to use https thus there will be a `name mismatch error` as the certificate does not match the hostname of the artifact repo host

Remark: I don't want to generally disable the checks but only for the update site so the `The Skip Certificate Check plugin` is not the solution for me

**Tags:** jenkins

> **Comments:**
> **username_1**: I don't think it is possible. Can you consider using certs signed by your own created CA, either on the artifact repo host or on a specific reverse proxy you control ?  
> **username_0**: Well I obviously can use self-signed certificates, but the problem is the host-name missmatch as the hostname of my repo server or reverse proxy is not `updates.jenkins-ci.org`  
> **username_2**: I would take a look at the following project and plugin:  https://github.com/jenkinsci/juseppe https://wiki.jenkins.io/display/JENKINS/UpdateSites+Manager+plugin  
> **username_0**: Thanks @username_2 didn't knew about this  

---

## 1 answers

### Answer by username_1 on 2019-05-28. Score: 0 | Accepted answer

Following your comment confirming you can use your own signed certificates internally.

One solution would be to replace the current certificate on your repo with a new one holding `updates.jenkins-ci.org` as an alias. [This response on stackoverflow](https://stackoverflow.com/questions/10175812/how-to-create-a-self-signed-certificate-with-openssl/27931596#27931596) has the necessary info to get you going.

Meanwhile, the [plugin higlighted above by @username_2 in the comments](https://wiki.jenkins.io/display/JENKINS/UpdateSites+Manager+plugin) (which I didn't know) seems to be a solution much easier to manage.


---

