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

Proxy authentication error 407 even if 'check proxy' works

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: In Review (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: core
    • Environment:
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            stephenconnolly Stephen Connolly added a comment -

            Ok, so Http URLs will populate the sun.net.www.protocol.http.AuthenticationInfo.cache.hashtable but Https URLs will not populate, only consult

            Show
            stephenconnolly Stephen Connolly added a comment - Ok, so Http URLs will populate the sun.net.www.protocol.http.AuthenticationInfo.cache.hashtable but Https URLs will not populate, only consult
            Hide
            stephenconnolly Stephen Connolly added a comment -

            FYI the workaround may only last for a short-ish period of time as the cache seems to get purged under circumstances I have been unable to determine

            Show
            stephenconnolly Stephen Connolly added a comment - FYI the workaround may only last for a short-ish period of time as the cache seems to get purged under circumstances I have been unable to determine
            Hide
            israelromero Israel Romero Fijo added a comment -

            Same issue with 2.107.2 version 

            Show
            israelromero Israel Romero Fijo added a comment - Same issue with 2.107.2 version 
            Hide
            harrygg Harry G. added a comment -

            For us it is fixed, probably either by removal of a duplicate update center we had (same update center twice, disappeared after update and restart) or with the update to 2.107.3 (possibly related in the changelog: "Add new update center root CA certificate. (INFRA-1502)" ?)

            Show
            harrygg Harry G. added a comment - For us it is fixed, probably either by removal of a duplicate update center we had (same update center twice, disappeared after update and restart) or with the update to 2.107.3 (possibly related in the changelog: "Add new update center root CA certificate. ( INFRA-1502 )" ?)
            Hide
            jyanesancert Jorge Yanes added a comment - - edited

            Still happens to me with 2.121.3, behind a proxy that requires NTLM or basic auth. I am using basic auth, but the password expired. I updated my proxy settings and although the proxy test check succeeds, the plugin manager was getting a 407 when checking for updates. I issued  

            ProxyConfiguration.open(new java.net.URL("http://jenkins.io")).content
            

            and that refreshed the caches and it's now working; I guess it will work until the password expires again. EDIT: never mind, restarting jenkins causes the 407 again, even if the credentials are right.

            Please don't dismiss this bug yet. How about adding a simple "ping" to an http resource to force the cache refresh?

            Show
            jyanesancert Jorge Yanes added a comment - - edited Still happens to me with 2.121.3, behind a proxy that requires NTLM or basic auth. I am using basic auth, but the password expired. I updated my proxy settings and although the proxy test check succeeds, the plugin manager was getting a 407 when checking for updates. I issued   ProxyConfiguration.open( new java.net.URL( "http: //jenkins.io" )).content and that refreshed the caches and it's now working; I guess it will work until the password expires again. EDIT: never mind, restarting jenkins causes the 407 again, even if the credentials are right. Please don't dismiss this bug yet. How about adding a simple "ping" to an http resource to force the cache refresh?

              People

              • Assignee:
                stephenconnolly Stephen Connolly
                Reporter:
                go Gerald Ortner
              • Votes:
                6 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated: