Hey guys, first time post in this subsection. I usually hang out in Networking.
So I run IIS8 on my home webserver and I'm wanting to allow public downloads of a subfolder. I have a physical folder on the server with directory browsing on and it works great for letting others download files from the webserver. Problem is, I have about 150GB of files that I want to share, but I don't want to physically put them on the server. I want to keep them on my Synology NAS where they are backed up and redundant. I created a virtual directory pointing to this share and when I test the username nad password it works great, and through IIS manager it lets me browse the directory. The problem is when you access it via the site, I get this:
I've tried googling it, but can't find anything on how to get it to work.
So I run IIS8 on my home webserver and I'm wanting to allow public downloads of a subfolder. I have a physical folder on the server with directory browsing on and it works great for letting others download files from the webserver. Problem is, I have about 150GB of files that I want to share, but I don't want to physically put them on the server. I want to keep them on my Synology NAS where they are backed up and redundant. I created a virtual directory pointing to this share and when I test the username nad password it works great, and through IIS manager it lets me browse the directory. The problem is when you access it via the site, I get this:
Code:
Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
I've tried googling it, but can't find anything on how to get it to work.