Plugin checkUpdates not working, can't upgrade plugins

[Craig Rodrigues]

Hi,

I have a Jenkins system running at https://jenkins.freebsd.org ,

and checking for plugin updates hasn't worked in 2 months and 19 days.

This Jenkins system has been upgraded to 1.656, and rebooted

several times, but it is still not working.

If I click on:
https://jenkins.freebsd.org/pluginManager/checkUpdates ,

I see a screen which shows, Checking updates....

but nothing happens, and the plugin information is not updated.

I don't see any errors in the Jenkins log files.

In addition, if I log into the host machine running Jenkins, I

can access https://updates.jenkins-ci.org/current/update-center.json

without a problem, so there don't seem to be any network connectivity

issues to the Jenkins updates site.

Any ideas what is wrong?

Thanks.

--

Craig

[Craig Rodrigues]

Hi,

This Jenkins system was set up behind an nginx reverse proxy.

After further analysis of nginx, I found this in nginx-errors.log:

Looking in /var/log/nginx-error.log , I found:

2016/04/08 09:38:35 [error] 1176#0: *834969 client intended to send too large body: 1079277 bytes, client: 8.8.178.110, server: jenkins.freebsd.org, request: "POST /updateCenter/byId/default/postBack HTTP/1.0", host: "jenkins.freebsd.org", referrer: "https://jenkins.freebsd.org/pluginManager/checkUpdates"

So it looks like 2 months ago, the update-center.json became big enough to trigger this problem.

Setting the client_max_body_size value as specified in https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy

solved the problem.

--

Craig

[Daniel Beck]

On 08.04.2016, at 20:46, Craig Rodrigues <rod...@FreeBSD.org> wrote:

> So it looks like 2 months ago, the update-center.json became big enough to trigger this problem.

We recommend you use the server-based download you can configure in the security options of Jenkins. It's been the default for a while now as well.