-
Bug
-
Resolution: Fixed
-
Major
-
Windows Server 2016, MSFT Docker, OpenJDK 8 Container
-
-
Jenkins 2.168
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.
- causes
-
JENKINS-56578 Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
-
- Open
-
- links to
[JENKINS-56114] Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Summary | Original: Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ | New: Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) |
Description |
Original:
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. |
New:
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. |
Description |
Original:
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. |
New:
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. |
Description |
Original:
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. |
New:
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. |
Description |
Original:
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. |
New:
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. |
Summary | Original: Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) | New: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) |
Description |
Original:
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. |
New:
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. |
Attachment | New: jenkins_dir_tree_20190213_1.txt [ 46014 ] |
Attachment | New: Screenshot_2019-02-25_140654_001.png [ 46184 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |