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

Error communicating to server! Server Error

    Details

    • Similar Issues:

      Description

      Getting Error communicating to server! Server Error. when using with multi branch pipeline

       

      Error while serving http://xxx.xxx.xxx.xxx:8080/view/Demo/api/json com.google.api.client.http.HttpResponseException: 403 Forbidden <html><head><meta http-equiv='refresh' content='1;url=/login?from=%2Fjob%2FDemo-Multibranch%2Fjob%2Fdevelopment%2Fwfapi%2Fruns'/><script>window.location.replace('/login?from=%2Fjob%2FDemo-Multibranch%2Fjob%2Fdevelopment%2Fwfapi%2Fruns');</script></head><body style='background-color:white; color:white;'> Authentication required <!-- You are authenticated as: anonymous Groups that you are in: Permission you need to have (but didn't): hudson.model.Hudson.Read ... which is implied by: hudson.security.Permission.GenericRead ... which is implied by: hudson.model.Hudson.Administer --> </body></html> at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1061) at se.diabol.jenkins.workflow.WorkflowApi.execute(WorkflowApi.java:79) at se.diabol.jenkins.workflow.WorkflowApi.getRunsFor(WorkflowApi.java:57) Caused: java.lang.IllegalStateException

        Attachments

          Issue Links

            Activity

            Hide
            brunoengcomp Bruno Lopes added a comment -

            Hi. I have the same error using "normal pipeline", with Jenkins authentication (LDAP). It seems that the plugin ignores that I'm logged in. In my opinion this is a blocker bug. Thanks in advance!

            ..................
            Authentication required
            <!--
            You are authenticated as: anonymous
            Groups that you are in:
             
            Permission you need to have (but didn't): hudson.model.Hudson.Read
             ... which is implied by: hudson.security.Permission.GenericRead
             ... which is implied by: hudson.model.Hudson.Administer
            -->

            </body></html>                                                                                                                                                                                                                                                                                                            
                at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1061)
                at se.diabol.jenkins.workflow.WorkflowApi.execute(WorkflowApi.java:79)
                at se.diabol.jenkins.workflow.WorkflowApi.getRunsFor(WorkflowApi.java:57)
            Caused: java.lang.IllegalStateException
                at se.diabol.jenkins.workflow.WorkflowApi.getRunsFor(WorkflowApi.java:61)

            Show
            brunoengcomp Bruno Lopes added a comment - Hi. I have the same error using "normal pipeline", with Jenkins authentication (LDAP). It seems that the plugin ignores that I'm logged in. In my opinion this is a blocker bug. Thanks in advance! .................. Authentication required <!-- You are authenticated as: anonymous Groups that you are in:   Permission you need to have (but didn't): hudson.model.Hudson.Read  ... which is implied by: hudson.security.Permission.GenericRead  ... which is implied by: hudson.model.Hudson.Administer --> </body></html>                                                                                                                                                                                                                                                                                                                 at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1061)     at se.diabol.jenkins.workflow.WorkflowApi.execute(WorkflowApi.java:79)     at se.diabol.jenkins.workflow.WorkflowApi.getRunsFor(WorkflowApi.java:57) Caused: java.lang.IllegalStateException     at se.diabol.jenkins.workflow.WorkflowApi.getRunsFor(WorkflowApi.java:61)
            Hide
            tommysdk Tommy Tynjä added a comment -

            This issue seems to be a duplicate of JENKINS-43797, where the pipeline view for Jenkins pipelines fails to render when Jenkins has authentication enabled. This was released in Delivery Pipeline plugin 1.0.3. Please upgrade to that version to see if it solves this issue.

            Show
            tommysdk Tommy Tynjä added a comment - This issue seems to be a duplicate of JENKINS-43797 , where the pipeline view for Jenkins pipelines fails to render when Jenkins has authentication enabled. This was released in Delivery Pipeline plugin 1.0.3. Please upgrade to that version to see if it solves this issue.

              People

              • Assignee:
                Unassigned
                Reporter:
                ahasnaini Asad Ali
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: