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

Clicking on "console" icon doesn't work

    XMLWordPrintable

Details

    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

            vikas027 Vikas Kumar added a comment -

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

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

            Merged to master, fixed in next release (1.4.9)

            dalvizu Dan Alvizu added a comment - Merged to master, fixed in next release (1.4.9)

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

            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.
            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?

            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?

            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.

            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

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

              Dates

                Created:
                Updated:
                Resolved: