In our development environment, we are using default media folder location.
But for Production/Live environment, we have two servers both are using same shared sql server database for umbraco.
But for media, when we try to use one common shared location "//networkshare/media", it throws following an exception
An error occurred while starting the application. DirectoryNotFoundException: \\networkshare\media\ Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(string root, ExclusionFilters filters)
We have set this media folder path in appsettings.json file as,
But our requirement is that, we have two server in load balancers which are using common SQL server database for umbraco. and we want to have both server access common share folder for media files.
But shared drive location for media file storage which we are trying are working properly now, just we need to give proper network access permissions to the IIS Application Pool.
Umbraco 13.4.1 and media folder location
Hi,
In our development environment, we are using default media folder location.
But for Production/Live environment, we have two servers both are using same shared sql server database for umbraco. But for media, when we try to use one common shared location "//networkshare/media", it throws following an exception
We have set this media folder path in appsettings.json file as,
What we are doing wrong ?
Kindly suggest solution for this problem.
cany you map the share to a drive or local folder maybe?
For local folder, it is working fine.
But our requirement is that, we have two server in load balancers which are using common SQL server database for umbraco. and we want to have both server access common share folder for media files.
Have you considered configuring your application to use Azure blob storage?
Hello All,
Thanks for your suggestions.
But shared drive location for media file storage which we are trying are working properly now, just we need to give proper network access permissions to the IIS Application Pool.
Thank You
is working on a reply...