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

Blue Ocean Test Results fail to load over https

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: blueocean-plugin
    • Labels:
      None
    • Environment:
      Jenkins v2.50 (running directly on a server; not containerized)
      Blue Ocean 1.0.0-rc1
      Google Chrome Version 56.0.2924.87 (64-bit)
    • Similar Issues:
    • Epic Link:
    • Sprint:
      Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4

      Description

      Test results that appear in the old Jenkins UI do not show in the Blue Ocean UI. This appears to be an issue because jenkins is running on https. Going directly to the link that fetch labels as 'Redirect Failed' works.

      Network Layout:

      Internet --> [F5] ---> [Jenkins]

      The F5 manages the SSL certs as well as redirecting to https.

      Below is the output from the chrome console:

      Mixed Content: The page at 'https://jenkins.madmobile.com/blue/organizations/jenkins/Concierge%2FConcierge%20Internal%20Build/detail/Concierge%20Internal%20Build/16/tests' was loaded over HTTPS, but requested an insecure resource 'http://jenkins.madmobile.com/blue/rest/organizations/jenkins/pipelines/Concierge/pipelines/Concierge%20Internal%20Build/runs/16/testReport/result/'. This request has been blocked; the content must be served over HTTPS.
      Fetch API cannot load https://jenkins.madmobile.com/blue/rest/organizations/jenkins/pipelines/Concierge/pipelines/Concierge%20Internal%20Build/runs/16/testReport/result. Redirect failed.
      Mixed Content: The page at 'https://jenkins.madmobile.com/blue/organizations/jenkins/Concierge%2FConcierge%20Internal%20Build/detail/Concierge%20Internal%20Build/16/tests' was loaded over HTTPS, but requested an insecure resource 'http://jenkins.madmobile.com/blue/organizations/jenkins/Concierge%2FConcierge%20Internal%20Build/detail/Concierge%20Internal%20Build/16/tests/'. This request has been blocked; the content must be served over HTTPS.
      

        Attachments

          Activity

          Hide
          michaelneale Michael Neale added a comment -

          I think har files are best not on a public ticket as it may contain more personal information than should be shared. 

          Show
          michaelneale Michael Neale added a comment - I think har files are best not on a public ticket as it may contain more personal information than should be shared. 
          Hide
          jamesdumay James Dumay added a comment -

          Unable to reproduce this with the given information. Please reopen if you can provide more info and thanks for reporting

          Show
          jamesdumay James Dumay added a comment - Unable to reproduce this with the given information. Please reopen if you can provide more info and thanks for reporting
          Hide
          elatt Erik Lattimore added a comment - - edited

          We have this issue as well. We have Jenkins sitting behind an nginx serving HTTPS for us. I see the same errors in the Chrome console talking about the trying to request information over an insecure resource.

          Show
          elatt Erik Lattimore added a comment - - edited We have this issue as well. We have Jenkins sitting behind an nginx serving HTTPS for us. I see the same errors in the Chrome console talking about the trying to request information over an insecure resource.
          Hide
          elatt Erik Lattimore added a comment -
          Show
          elatt Erik Lattimore added a comment - I've configured our nginx settings as follows:  https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy  
          Hide
          elatt Erik Lattimore added a comment -

          Actually, I believe our nginx configuration was incorrect. I updated the settings to what was on the wiki and we are no longer getting the insecure resource errors and the page now displays.

          Show
          elatt Erik Lattimore added a comment - Actually, I believe our nginx configuration was incorrect. I updated the settings to what was on the wiki and we are no longer getting the insecure resource errors and the page now displays.

            People

            • Assignee:
              jamesdumay James Dumay
              Reporter:
              loljs Jonathan Brito
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: