A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
Hi Marc
It sounds like you don't have Sticky Sessions enabled and the load balancer lead you to a different server than the one that generated the export file.
You can either:
I personally prefer the first option.
Hi Stefan
I found an open feature request that would make it possible to support this without sticky sessions: Possible to export data in load balanced environment with non-sti (episerver.com)
Supporting sticky sessions is not straightforward in our environment. We use a Application Gateway / Service Fabric setup.
We'll implement the first option, deploying a single-instance edit site. Downside is this extra instance will also count in for our cloud license.
Hello
We're migrating our CMS (11.20) to Azure. Exporting content from the admin site does not seem to work.
It seems the export is generated in the user's temp folder (e.g. c:\windows\temp\). We tried to change this path to a fileshare which is common to all CMS nodes. The export is generated but can't be downloaded in the UI.
Are we missing something? Is this a supported scenario? Or does this only work with sticky sessions?
How can we fix this while keeping the multi-node setup?
Regards
Marc
--
EPiServer.CMS: 11.20.0
EPiServer.CMS.UI: 11.30.0