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

Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      Jenkins 2.168

      Description

      Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

      After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

      HTTP ERROR 403

      Problem accessing /job/<job_name_redacted>/ws/. Reason:

      Trying to access a file outside of the directory, target:

       


      Powered by Jetty:// 9.4.z-SNAPSHOT

       

      Attempted upgrade of container to OpenJDK 11, same errors occur.

      Job artifacts are created and present on local file system.  Workspace is created and present on local file system.  Job will build project, just won't present the results/workspace through the UI.

      Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.

      IIS reverse proxy reference:  https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+IIS (instead of localhost and host file, used container IP address directly).  Tested as working in 2.138, fails on 2.150.2+, works correctly when reverted to 2.138.

        Attachments

          Issue Links

            Activity

            jkam Jeremy Kam created issue -
            jkam Jeremy Kam made changes -
            Field Original Value New Value
            Summary Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
            jkam Jeremy Kam made changes -
            Description Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible as expected.

            After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

            "Problem accessing /job/<jobname>/ws/. Reason:

            Trying to access a file outside of the directory, target:"

            Attempted upgrade of container to OpenJDK 11, same errors occur.

            Job artifacts are created and present on local file system.  Workspace is created and present on local file system.
            Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible as expected.

            After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

            "Problem accessing /job/<jobname>/ws/. Reason:

            Trying to access a file outside of the directory, target:"

            Attempted upgrade of container to OpenJDK 11, same errors occur.

            Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

            Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
            jkam Jeremy Kam made changes -
            Description Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible as expected.

            After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

            "Problem accessing /job/<jobname>/ws/. Reason:

            Trying to access a file outside of the directory, target:"

            Attempted upgrade of container to OpenJDK 11, same errors occur.

            Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

            Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
            Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

            After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

            "Problem accessing /job/<jobname>/ws/. Reason:

            Trying to access a file outside of the directory, target:"

            Attempted upgrade of container to OpenJDK 11, same errors occur.

            Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

            Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
            jkam Jeremy Kam made changes -
            Description Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

            After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

            "Problem accessing /job/<jobname>/ws/. Reason:

            Trying to access a file outside of the directory, target:"

            Attempted upgrade of container to OpenJDK 11, same errors occur.

            Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

            Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
            Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

            After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
            h2. HTTP ERROR 403

            Problem accessing /job/<job_name_redacted>/ws/. Reason:

            Trying to access a file outside of the directory, target:

             
            ----
            [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty]

             

            Attempted upgrade of container to OpenJDK 11, same errors occur.

            Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

            Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
            jkam Jeremy Kam made changes -
            Description Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

            After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
            h2. HTTP ERROR 403

            Problem accessing /job/<job_name_redacted>/ws/. Reason:

            Trying to access a file outside of the directory, target:

             
            ----
            [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty]

             

            Attempted upgrade of container to OpenJDK 11, same errors occur.

            Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

            Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
            Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

            After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
            h2. HTTP ERROR 403

            Problem accessing /job/<job_name_redacted>/ws/. Reason:

            Trying to access a file outside of the directory, target:

             
            ----
            [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty]

             

            Attempted upgrade of container to OpenJDK 11, same errors occur.

            Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

            Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.

            IIS reverse proxy reference:  [https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+IIS] (instead of localhost and host file, used container IP address directly).  Tested as working in 2.138, fails on 2.150.2+, works correctly when reverted to 2.138.
            jkam Jeremy Kam made changes -
            Summary Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
            jkam Jeremy Kam made changes -
            Description Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

            After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
            h2. HTTP ERROR 403

            Problem accessing /job/<job_name_redacted>/ws/. Reason:

            Trying to access a file outside of the directory, target:

             
            ----
            [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty]

             

            Attempted upgrade of container to OpenJDK 11, same errors occur.

            Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

            Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.

            IIS reverse proxy reference:  [https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+IIS] (instead of localhost and host file, used container IP address directly).  Tested as working in 2.138, fails on 2.150.2+, works correctly when reverted to 2.138.
            Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

            After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
            h2. HTTP ERROR 403

            Problem accessing /job/<job_name_redacted>/ws/. Reason:

            Trying to access a file outside of the directory, target:

             
            ----
            [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty]

             

            Attempted upgrade of container to OpenJDK 11, same errors occur.

            Job artifacts are created and present on local file system.  Workspace is created and present on local file system.  Job will build project, just won't present the results/workspace through the UI.

            Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.

            IIS reverse proxy reference:  [https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+IIS] (instead of localhost and host file, used container IP address directly).  Tested as working in 2.138, fails on 2.150.2+, works correctly when reverted to 2.138.
            jkam Jeremy Kam made changes -
            Attachment jenkins_dir_tree_20190213_1.txt [ 46014 ]
            wfollonier Wadeck Follonier made changes -
            wfollonier Wadeck Follonier made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            wfollonier Wadeck Follonier made changes -
            Assignee Wadeck Follonier [ wfollonier ]
            wfollonier Wadeck Follonier made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            danielbeck Daniel Beck made changes -
            Labels lts-candidate
            wfollonier Wadeck Follonier made changes -
            Remote Link This issue links to "#3914 in core (Web Link)" [ 22433 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue causes JENKINS-56578 [ JENKINS-56578 ]
            oleg_nenashev Oleg Nenashev made changes -
            Released As Jenkins 2.168
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Resolved [ 5 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels lts-candidate causes-regression lts-candidate
            danielbeck Daniel Beck made changes -
            Labels causes-regression lts-candidate lts-candidate regression
            danielbeck Daniel Beck made changes -
            Labels lts-candidate regression causes-regression lts-candidate regression
            olivergondza Oliver Gondža made changes -
            Labels causes-regression lts-candidate regression 2.164.2-fixed causes-regression regression

              People

              Assignee:
              wfollonier Wadeck Follonier
              Reporter:
              jkam Jeremy Kam
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: