Dmitry Esarev added a comment - 2017-04-14 06:12 - edited GET-request.txt.zip postBack.txt.zip yes, actually there is an postback error when sniffering through dev console: 1. On GET request https://updates.jenkins-ci.org/current/update-center.json.html?id=default&version=2.53 The headers are: Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 Accept-Encoding:gzip, deflate, sdch, br Accept-Language:en-US,en;q=0.8,ru;q=0.6,zh;q=0.4 Connection:keep-alive Host:updates.jenkins-ci.org If-Modified-Since:Fri, 14 Apr 2017 05:32:56 GMT If-None-Match: "117316-54d19c619320f-gzip" Referer:http: //jenkins.vm.mycorp.local/pluginManager/checkUpdates Upgrade-Insecure-Requests:1 User-Agent:Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 And the whole request body file-attached as : GET-request.txt.zip (it has json pretty-formatted for readability) 2. And then i'v got a respone with Status Code:413 Request Entity Too Large. And the whole response body file-attached as postBack.txt.zip (it has json pretty-formatted for readability)

Dmitry Esarev added a comment - 2017-04-14 06:25 - edited Thank you for the tips. I have it fixed by configuring client_max_body_size of the nginx: # vi /etc/nginx/sites-enabled/jenkins server { client_max_body_size 10m; ... # service nginx restart this parameter is also documented here https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Nginx

Daniel Beck added a comment - 2017-04-14 13:36 The browser-based metadata download has been deprecated as being unsafe and unreliable years ago. There should have been an admin monitor warnings against its use. Seems you dismissed it?

Dmitry Esarev added a comment - 2017-04-14 15:40 i actually dont remember. it is possible i somehow mute it. And now what should i do?

Daniel Beck added a comment - 2017-04-14 16:06 Well, you worked around it. Nothing I suppose? But you can still disable the option in the security configuration.