[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam 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 403Problem accessing /job//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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam 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/< jobname 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam 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//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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam 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//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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+
Title: Message Title Jeremy Kam created an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-13 00:19 Environment: Windows Server 2016, MSFT Docker, OpenJDK 8 Container Priority: Major Reporter: Jeremy Kam 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//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. Add Comment
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam Summary: Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
