I installed a new database (once again) and also installed all files to the root again. This time I called default.aspx in the root directory to install. I had to copy siteurls.config from /config to root and voila, DNN works on my shaby 1and1 environment now. It is good to have the DNN install in the root; this way there is no unnecessary subdirectory in the url. Once again thanks for your deep explorations in this matter, Frank!

Regards

Tim

Hello there all,

I'm new to 1and1, but not new to DNN. Was able to install it very easily on a local win2k3 server.

But on 1and1, I'm getting security exceptions left and right. The only I'm doing different is leaving dotnetnuke in a subdirectory.

I am also following the 1and1 FAQ for 3.0.13 to try to keep the icing on the cake. I've been able to get the sucker installed. But I get security in different places. For example, I tried to change some basic host settings(putting in a SMTP server).  I was able to see the page full of options, then after trying to save I got a security exception. Now I can't even get to the host settings without a security exception.

I also get this when I try to modify some modules.

To minimize the security errors, I would install at the root of your webspace. 1and1 does not support dotnetnuke higher than 3.3 (i think).  As mentioned I don't think this is necessarily ALL 1and1's problems.  I think it's a combination of DNN, 1and1's security configuration, and the 2.0 Framework.  1and1's security configuration does not allow a web application to access files outside of the applications base domain directory. For good reason; because I could then write a program/webpage that could traverse the entire hard drive and I could see your web.config file with your DNN credentials in the connection string parameter. But from some strange reason, on 1and1 servers , the DNN baseline forgets where it's home directory is, and .Net thinks you are trying to access a file/folder outside your appdomain.

I think if we could create our own virtual directories on 1and1 servers with our own apppools the problem would go away but I'm just guessing.  I'm think other webhosts allow you to create REAL virtual directories.  I have no idea what the 1and1 "webfiles" application is really doing behind the scenes, but that thing seems a little suspect to me.

 Follow our instructions to install at the root and you should see alot less security errors.