This definitely sounds like something environmental.  It's usually really easy to get things up and running these days.  Back before version ~6, that wasn't necessarily the case.  (Not necessarily because of anything specific in DNN, but all of the dependencies are either preinstalled, or all work together better than they used to.)  

Also, my experience with any of the control panel software used on a server is a mixed bag.  I almost always end up having to do something manually, depending on what's being hosted.  I tend to not use any of them these days, unless there are others I want to have access to the server.  (That is, when it's not in Azure.)  

Thanks Will, I've escalated the case with hosting support. I'm coming from my own Plesk server to theirs and was expecting this to be much smoother. I'm hoping they find something in the config bugged out and can fix it.

You'll want to be sure all of the prerequisites are in place, and also confirm that you can assign (and use) the required permissions.  By the way, these requirements are not unique to DNN.  These are generally the same requirements for most ASP.NET applications.  So, they can hopefully help you figure things out.  

Ok this looks like it was Web Application Firewall in Plesk that was blocking the requested files causing the 403 errors.

Posted By Andrew on 10/11/2023 5:29 PM
Ok this looks like it was Web Application Firewall in Plesk that was blocking the requested files causing the 403 errors.

Yeah, those things get in my way all of the time. It's awesome you found the fix.  Thank you for letting us know!  💪🏽 

 

How is easier to install it?