I've spent all day on this. Right now Im getting this from www.dnndev.me
Why has no one created a docker with this all set up?
The account that runs the application pool needs access to the database. Saying that: it depends how you have set it up.
First I would try to check if the connection works. You could use telnet Iin a command window or PoswerShell) to find out:
telnet servername port
A default instance would run on port 1433, but if you have setup a named instance you have to check the port number.
If no: check the firewall.
If the connection is working (empty screen in the command window), check the permissions of the application pool account. Start by adding the user to the db_owner role, but strengthen security by the advisories in this blog article.
Michael TobischDNN★MVP
Posted By Profk on 1/20/2023 1:58 PM Why has no one created a docker with this all set up?
First... Welcome to the community!
One of the main reasons behind this is maybe something you'll soon discover... DNN is such a configurable application, that installing and configuring it a single way for everyone would in some ways make it seem like DNN is less flexible. It's always been an idea that comes back up from time to time though.
In the future, something that would help make local DNN installations faster & easier would be nvQuickSite. :)
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.