Published Folders Not Working in 2026.2.0
Looks like Published Folders stopped working. I'm seeing this repeated in the system logs.
2026-06-01 09:38:01.561 -05:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request starting HTTP/2 GET https://dev-universal.xxxxxx.com/login?returnUrl=/admin/platform/publishedFolders - null null
2026-06-01 09:38:01.566 -05:00 [INF][Microsoft.AspNetCore.Authentication.Cookies.CookieAuthenticationHandler] Cookies was not authenticated. Failure message: Identity missing in session store
2026-06-01 09:38:01.580 -05:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executing endpoint '/Login'
2026-06-01 09:38:01.580 -05:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Route matched with {page = "/Login", action = "", controller = ""}. Executing page /Login
2026-06-01 09:38:01.583 -05:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executing handler method PowerShellUniversal.Login.OnGet - ModelState is "Valid"
2026-06-01 09:38:01.690 -05:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed handler method OnGet, returned result Microsoft.AspNetCore.Mvc.RazorPages.PageResult.
2026-06-01 09:38:01.692 -05:00 [INF][Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvoker] Executed page /Login in 109.4217ms
2026-06-01 09:38:01.693 -05:00 [INF][Microsoft.AspNetCore.Routing.EndpointMiddleware] Executed endpoint '/Login'
2026-06-01 09:38:01.693 -05:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 GET https://dev-universal.xxxxxx.com/login?returnUrl=/admin/platform/publishedFolders - 200 null text/html; charset=utf-8 129.376msAll Comments (2)
@dbytes I moved this into a bug report. I'm assuming you are just using a standard published folder with authentication? Are you accessing it via a browser or some other way?
Adam Driscoll
PowerShell Expert and Developer at Devolutions
@Adam Driscoll, correct just a standard published folder to serve up some images. Both authenticated and unauthenticated, with roles and without. Accessing it with the browser and also have the admin console pointing to it for branding.