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

Https redirection is not triggerring the FQDN but the @IP instead

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: schedule-build-plugin
    • Labels:
      None
    • Environment:
      Jenkins verion 2.89.3
      Plugin schedule-build, version: 0.5.1
      CentOS Linux release 7.4.1708
    • Similar Issues:

      Description

      Https redirection is not triggerring the FQDN but the @IP instead. Exemple : https://84.39.xx.xxx/jenkins/view/All/job/ClusterUpgradeWebcomwsWithStopAndStart/

      SInce my Jenkins setup user identification is retrieved from HTTP Header by reverse proxy, https redirection is blocked for security alert i.e. the redirect https URL based on public @IP is not matching the FQDN based built LetsEncrypt certificate.

      Why don't you trigger the former Jenkins URL based on FQDN. Exemple : https://ip-84-39-xx-xxx.rev.cloudwatt.com/jenkins/view/All/job/ClusterUpgradeWebcomwsWithStopAndStart/

       

      Thanks for your help.

      Best Regards. Richard

        Attachments

          Activity

          Hide
          pingunaut Martin Spielmann added a comment - - edited

          Hi Richard CARRE,

          The plugin uses the absoluteUrl property of a job to do the redirect, so there shouldn't be any redirect from Hostname to IP.

          Please check if you set the Jenkins URL (https://HOSTNAME.../jenkins) in Manage Jenkins ->  Configure System.

          If you are running jenkins behind a reverse proxy, please check if the config is correct (see https://wiki.jenkins.io/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken).

          If the problem persists, please provide details of the requests and responses beeing sent by your browser during the redirects.

          Best regards,

          Martin

           

          Show
          pingunaut Martin Spielmann added a comment - - edited Hi Richard CARRE , The plugin uses the absoluteUrl property of a job to do the redirect, so there shouldn't be any redirect from Hostname to IP. Please check if you set the Jenkins URL ( https://HOSTNAME.../jenkins ) in Manage Jenkins ->  Configure System. If you are running jenkins behind a reverse proxy, please check if the config is correct (see https://wiki.jenkins.io/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken ). If the problem persists, please provide details of the requests and responses beeing sent by your browser during the redirects. Best regards, Martin  
          Hide
          orich Richard CARRE added a comment -

          Misconfiguration of Jenkins URL (https://HOSTNAME.../jenkins) in Manage Jenkins ->  Configure System

          Show
          orich Richard CARRE added a comment - Misconfiguration of Jenkins URL ( https://HOSTNAME.../jenkins ) in Manage Jenkins ->  Configure System
          Hide
          orich Richard CARRE added a comment -

          Many thanks Martin

          Show
          orich Richard CARRE added a comment - Many thanks Martin
          Hide
          pingunaut Martin Spielmann added a comment - - edited

          Alright. Richard CARRE Thanks a lot for your feedback

          Show
          pingunaut Martin Spielmann added a comment - - edited Alright. Richard CARRE Thanks a lot for your feedback

            People

            Assignee:
            pingunaut Martin Spielmann
            Reporter:
            orich Richard CARRE
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: