Facebook
Twitter
R
redherring8451
Guest
Hi. We need to be able to create a virtual directory for one site that points to the physical directory of another site. So, the path we want for the virtual directory is like "../stores.othersite.com/httpdocs/wwwapp".
The Plesk Contral Panel will not let us do this, stating that this "Physical path is invalid or does not exist". It does in fact exist and is valid, but Plesk seems to want to lock virtual directory path references down to the physical directory structure of the actual site in question only.
Since this ability is a requirement for us and our application, we went outside of Plesk and set up this virtual directory in IIS where the desired path was allowed. This "worked" except that when you attempt to browse to the virtual directory (in a browser) it requires authentication.
We have verified the security for the above mentioned physical directory and we can browse to it directly but when we try browsing the same folder through the virtual directory, it asks for a log in. We've also confirmed that the settings are the same in IIS for the new virtual directory as they are for other Plesk-generated virtual directories.
After creating the virtual directory in IIS, if we go back into Plesk we can see that Plesk does recognize the existence of this new virtual directory, and it does show the desired path. We can also see that the "allow anonymous access" box is checked. But we can't make any changes within Plesk to this virtual directory, nor can we even click "ok" without it telling us that this "Physical path is invalid or does not exist". So, even though we appear to have done what needed to be done outside of Plesk in IIS, perhaps by doing so something doesn't "take" well that then makes the virtual directory require authentication for all users.
The Plesk Contral Panel will not let us do this, stating that this "Physical path is invalid or does not exist". It does in fact exist and is valid, but Plesk seems to want to lock virtual directory path references down to the physical directory structure of the actual site in question only.
Since this ability is a requirement for us and our application, we went outside of Plesk and set up this virtual directory in IIS where the desired path was allowed. This "worked" except that when you attempt to browse to the virtual directory (in a browser) it requires authentication.
We have verified the security for the above mentioned physical directory and we can browse to it directly but when we try browsing the same folder through the virtual directory, it asks for a log in. We've also confirmed that the settings are the same in IIS for the new virtual directory as they are for other Plesk-generated virtual directories.
After creating the virtual directory in IIS, if we go back into Plesk we can see that Plesk does recognize the existence of this new virtual directory, and it does show the desired path. We can also see that the "allow anonymous access" box is checked. But we can't make any changes within Plesk to this virtual directory, nor can we even click "ok" without it telling us that this "Physical path is invalid or does not exist". So, even though we appear to have done what needed to be done outside of Plesk in IIS, perhaps by doing so something doesn't "take" well that then makes the virtual directory require authentication for all users.
