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

Ajax blocked due to http/https mismatch in client side update check

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • core
    • Jenkins 2.77

      Setup

      Due to firewall restrictions I'm using the "Use Browser to download Meta Data" feature.

      This allowed me in the past to view all updates available for jenkins, even though the server itself has no internet access.

      Issue

      Since the last update to 2.77 this feature stopped working.
      When opening the browser console I get the following error:

      Mixed Content: The page at 'https://xxxx/sbjenkins/pluginManager/checkUpdates' was loaded over HTTPS, but requested an insecure resource 'http://updates.jenkins-ci.org/update-center.json.html?id=default&version=2.77'. This request has been blocked; the content must be served over HTTPS.

          [JENKINS-47019] Ajax blocked due to http/https mismatch in client side update check

          Oleg Nenashev added a comment -

          rtyler danielbeck Likely it has been caused by https://github.com/jenkinsci/jenkins/pull/2996 .

          Probably the update center configuration in Jenkins needs to be updated in order to use the HTTPS address.

          Oleg Nenashev added a comment - rtyler danielbeck Likely it has been caused by https://github.com/jenkinsci/jenkins/pull/2996 . Probably the update center configuration in Jenkins needs to be updated in order to use the HTTPS address.

          Daniel Beck added a comment -

          I'm pretty sure this is a legacy setup that has an HTTP update site URL configured.

          davidgiga1993 Manage Jenkins » Manage Plugins » Advanced. What's the URL at the bottom? What happens when you specify the equivalent https url?

          Daniel Beck added a comment - I'm pretty sure this is a legacy setup that has an HTTP update site URL configured. davidgiga1993 Manage Jenkins » Manage Plugins » Advanced. What's the URL at the bottom? What happens when you specify the equivalent https url?

          David S added a comment -

          danielbeck Doh, this fixes the issue. Sorry for overlooking that option. I was assuming the protocol changes automaticaly when you define "https" as jenkins URL.

          David S added a comment - danielbeck Doh, this fixes the issue. Sorry for overlooking that option. I was assuming the protocol changes automaticaly when you define "https" as jenkins URL.

          Daniel Beck added a comment -

          User configuration.

          Daniel Beck added a comment - User configuration.

            Unassigned Unassigned
            davidgiga1993 David S
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: