Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-59441

Jenkins can't reach update json despite browser load it correctly

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • _unsorted
    • Jenkins latest; no plugins; Windows Server 2016 Standard; Any web browser; Oracle JDK1.8;

      Brand new Jenkins instance is behind corporate proxy. Test URL passed, but checking plugins ends in "There were errors checking the update sites: FileNotFoundException: http://updates.jenkins.io/update-center.json?id=default&version=2.176.3", see screenshots.

      This URL is normally available in browser. When "Use browser for metadata download" ticked, I'm able to browse plugins but I can't download anything. I tried update mirrors (mirror.serverion.com) as update URL but still nothing. 

          [JENKINS-59441] Jenkins can't reach update json despite browser load it correctly

          Bartlomiej Chrabaszcz created issue -
          Bartlomiej Chrabaszcz made changes -
          Attachment New: error_log.txt [ 48813 ]
          Bartlomiej Chrabaszcz made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          ikedam made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: update-sites-manager-plugin [ 17576 ]

          Josh Soref added a comment -

          Josh Soref added a comment - Did you read https://wiki.jenkins.io/display/JENKINS/JenkinsBehindProxy ?

          Josh Soref added a comment -

          Also, I'm puzzled by your statement that you're using a brand new instance. I'd expect you to be using https://updates.jenkins.io/ (note the https). Can you explain why that s is missing?

          Josh Soref added a comment - Also, I'm puzzled by your statement that you're using a brand new instance. I'd expect you to be using  https://updates.jenkins.io/ (note the http s ). Can you explain why that s  is missing?

          Oleg Nenashev added a comment -

          It might be a temporary mirror issue though we need more information to triage it

          Oleg Nenashev added a comment - It might be a temporary mirror issue though we need more information to triage it
          Oleg Nenashev made changes -
          Component/s New: _unsorted [ 19622 ]
          Component/s Original: core [ 15593 ]

          Tim Jacomb added a comment -

          There was a change made to the update site which broke it on http,

          It's highly recommended to run it on https.

          But that specific change was reverted

          Tim Jacomb added a comment - There was a change made to the update site which broke it on http, It's highly recommended to run it on https. But that specific change was reverted
          Tim Jacomb made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Unassigned Unassigned
            baca90 Bartlomiej Chrabaszcz
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: