You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we have a shared web hosting server, and we are trying to provide nodejs hosting to a client, the issue here is the physical path is c:\websites\username\wwwroot but the nodejs is failing on the fact that it doesnt have rights to this websites folder. To preserve the security on the individual websites you normally should not give access to iusr acct of the root folder, as then effectively any app pool will gain those rights as well surely, iis sites works all fine with the rights as they are, is there a way to resolve this issue without assigning rights or what would the best method be to rectify this issue.
by creating a site in the root folder of the drive and giving the app pool full rights then the site works fine, so this is a rights issues, we dont want to start changing the file structure now as it is provisioned automatically under this websites folder.
The text was updated successfully, but these errors were encountered:
we have a shared web hosting server, and we are trying to provide nodejs hosting to a client, the issue here is the physical path is c:\websites\username\wwwroot but the nodejs is failing on the fact that it doesnt have rights to this websites folder. To preserve the security on the individual websites you normally should not give access to iusr acct of the root folder, as then effectively any app pool will gain those rights as well surely, iis sites works all fine with the rights as they are, is there a way to resolve this issue without assigning rights or what would the best method be to rectify this issue.
by creating a site in the root folder of the drive and giving the app pool full rights then the site works fine, so this is a rights issues, we dont want to start changing the file structure now as it is provisioned automatically under this websites folder.
The text was updated successfully, but these errors were encountered: