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

Clicking on "console" icon doesn't work

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When running the build pipeline and clicking the "console" icon the modal window only shows (in Chrome) "Unable to resolve the server's DNS address." The problem is that clicking on the "console" icon tries to load the following address which obviously doesn't work:

      http://job/JobName/71/console

        Attachments

          Issue Links

            Activity

            Hide
            vikas027 Vikas Kumar added a comment -

            Nicolas BOHEAS Thanks for the tip . Changing the Console Output Link Style from Lightbox to New Window or Same Window works fine.

            Show
            vikas027 Vikas Kumar added a comment - Nicolas BOHEAS Thanks for the tip . Changing the Console Output Link Style from Lightbox to New Window or Same Window works fine.
            Hide
            dalvizu Dan Alvizu added a comment -

            Merged to master, fixed in next release (1.4.9)

            Show
            dalvizu Dan Alvizu added a comment - Merged to master, fixed in next release (1.4.9)
            Hide
            ljohnston Lance Johnston added a comment -

            Just tried with 1.4.9 and Jenkins 1.609.2 and this does not appear to be fixed.

            Show
            ljohnston Lance Johnston added a comment - Just tried with 1.4.9 and Jenkins 1.609.2 and this does not appear to be fixed.
            Hide
            dalvizu Dan Alvizu added a comment -

            Are you seeing the same error above or a different one? Have you set your jenkins URL in system configuration?

            Show
            dalvizu Dan Alvizu added a comment - Are you seeing the same error above or a different one? Have you set your jenkins URL in system configuration?
            Hide
            ljohnston Lance Johnston added a comment -

            Indeed, the problem turned out to be related to the jenkins URL in the system configuration. Specifically, my apache reverse proxy was down and I was using the direct jenkins url, bypassing the one in the system configuration, when I encountered this problem. Once the reverse proxy was back up, console output started working again.

            Show
            ljohnston Lance Johnston added a comment - Indeed, the problem turned out to be related to the jenkins URL in the system configuration. Specifically, my apache reverse proxy was down and I was using the direct jenkins url, bypassing the one in the system configuration, when I encountered this problem. Once the reverse proxy was back up, console output started working again.

              People

              • Assignee:
                dalvizu Dan Alvizu
                Reporter:
                johanhaleby Johan Haleby
              • Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: