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

Proxy authentication error 407 even if 'check proxy' works

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core

      Proxy configuration doesn't work even if 'check proxy' works! No workaround found.

      Situation: Fresh installed Windows Server 2016 with latest, fresh installed  LTS Jenkins version 2.89.2. Server is behind a proxy. Check of Jenkins proxy configuration says 'Ok' but checking plugins crashes jenkins (see attached screen shot).

      I have a second machine (Windows 7 enterprise) with the same Jenkins version, behind the same proxy, with (really!) the same proxy configuration: Check Jenkins proxy settings says: "Error 407", BUT: Checking plugins works! (WTF!?!) One differrence is the java runtime verision: on this machine = 1.8.0_66-b18.

          [JENKINS-48775] Proxy authentication error 407 even if 'check proxy' works

          Gerald Ortner created issue -

          From the release notes:

          Default the built-in Jenkins Update Center URL to https://updates.jenkins.io instead of obsolete HTTP endpoint. This requires a JRE compatible with Let's Encrypt, e.g. Oracle JRE 8u101.

          i.e. as you mention, the Java version makes a difference.

          Christopher Orr added a comment - From the  release notes : Default the built-in Jenkins Update Center URL to https://updates.jenkins.io instead of obsolete HTTP endpoint. This requires a JRE compatible with Let's Encrypt , e.g. Oracle JRE 8u101. i.e. as you mention, the Java version makes a difference.
          Christopher Orr made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

          Gerald Ortner added a comment -

          Hi Christopher,

          at first thank you for your fast answer!
          Unfortunately, the situation on my both Jenkins servers is inverted: That one with JRE 1.8.0_66-b18 is working and the one with 1.8.0_144-b01 isn't working. Even the 'proxy check' is the other way around.

          bg Gerald

           

          Gerald Ortner added a comment - Hi Christopher, at first thank you for your fast answer! Unfortunately, the situation on my both Jenkins servers is inverted: That one with JRE 1.8.0_66-b18 is working and the one with 1.8.0_144-b01 isn't working. Even the 'proxy check' is the other way around. bg Gerald  

          Gerald Ortner added a comment -

          due to the situation that the Jenkins Server with the newer JRE makes the troubles => still an issue.

           

          Gerald Ortner added a comment - due to the situation that the Jenkins Server with the newer JRE makes the troubles => still an issue.  
          Gerald Ortner made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]
          Gerald Ortner made changes -
          Description Original: Proxy configuration doesn't work even if 'check proxy' works! No workaround found.

          Situation: Fresh installed Windows Server 2016 with latest, fresh installed  LTS Jenkins version 2.89.2. Server is behind a proxy. Check of Jenkins proxy configuration says 'Ok' but checking plugins crashes jenkins (see attached screen shot).

          I have a second machine (Windows 7 enterprise) with the same Jenkins version, behind the same proxy, with (really!) the same proxy configuration: Check Jenkins proxy settings says: "Error 407", BUT: Checking plugins works! (WTF!?!) One differrence is the jave runtime verision: on this machine = 1.8.0_66-b18.
          New: Proxy configuration doesn't work even if 'check proxy' works! No workaround found.

          Situation: Fresh installed Windows Server 2016 with latest, fresh installed  LTS Jenkins version 2.89.2. Server is behind a proxy. Check of Jenkins proxy configuration says 'Ok' but checking plugins crashes jenkins (see attached screen shot).

          I have a second machine (Windows 7 enterprise) with the same Jenkins version, behind the same proxy, with (really!) the same proxy configuration: Check Jenkins proxy settings says: "Error 407", BUT: Checking plugins works! (WTF!?!) One differrence is the java runtime verision: on this machine = 1.8.0_66-b18.
          R. Tyler Croy made changes -
          Rank New: Ranked higher
          R. Tyler Croy made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: core [ 21134 ]
          Component/s Original: update-center [ 22120 ]
          Key Original: INFRA-1455 New: JENKINS-48775
          Workflow Original: classic default workflow [ 224912 ] New: JNJira + In-Review [ 224949 ]
          Project Original: Infrastructure [ 10301 ] New: Jenkins [ 10172 ]

          Gerald Ortner added a comment -

          Hi rtyler,

          I have new gained insights of this problem:

          After consulting out IT guys, it was clear that the Jenkins server DON'T send any authentication to the proxy (maybe except when pressing 'check proxy').
          So there were made two configurations on the company proxy server:
          1. added 'https://updates.jenkins.io' to the 'DoNotAuthenticate whitelist'
          2. turned off the 'SSL Interception' for this URL
          Now, with this workaround, checking and downloading plugin works! But that can't be the final solution!

          Thank you for your effort!

          BG Gerald

           

          Gerald Ortner added a comment - Hi rtyler, I have new gained insights of this problem: After consulting out IT guys, it was clear that the Jenkins server  DON'T send any authentication to the proxy (maybe except when pressing 'check proxy'). So there were made two configurations on the company proxy server: 1. added ' https://updates.jenkins.io'  to the 'DoNotAuthenticate whitelist' 2. turned off the 'SSL Interception' for this URL Now, with this workaround, checking and downloading plugin works! But that can't be the final solution! Thank you for your effort! BG Gerald  

            Unassigned Unassigned
            go Gerald Ortner
            Votes:
            7 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: