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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • schedule-build-plugin
    • None
    • Jenkins verion 2.89.3
      Plugin schedule-build, version: 0.5.1
      CentOS Linux release 7.4.1708

      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

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

              Created:
              Updated:
              Resolved: