Hello,

I recently had my host install a copy of DotNetNuke on a shared account. It was installed in a subfolder, i.e. 'www.site.com'. Prior to making a change to the Portal Alias list, I was able to access the site via "IP_Address/folder_name". I wanted to be able to access the site via "domain_name" and my host was not very helpful, only saying that something in the DNN config was "redirecting" to the IP-based address.

I did a little research and found the Portal Alias information. Upon looking at the default settings, the only Alias configured was "IP_Address/folder_name", so I thought I had found the culprit. I added two aliases, 'www.site.com' and 'site.com'. I couldn't edit the default Alias, and read that was because I had logged in on that Alias. I restarted DNN and there was no change.

I then directly edited the database table, removing the IP-based Alias entry. Now I can't access the site at all. I also can't add back the IP-based entry to the database, so my site is now completely broken.

Help!

Chris

Hi JK,

Thanks for the reply.

I "pinged" the site and the IP came back ok. The hosting account is set to associate requests for the 'site.com' address to the correcto subfolder.

Trying to add the Alias back to the database was a stopgap repair. I get a permissions error, but at this point, I would rather get the thing fixed right rather than add a bogus alias back in just to get the site working again.

Here's what I think happened:

The host setup the site with a default alias that was not appropriate for the site. The aliases are now correct, but since I can't restart the site, I'm SOL.

The host claims that it's something in my "web.config" file messing things up, external to the DNN install. What they don't seem to realize is that the only reason there's a "web.config" file in the site in the first place is because of the DNN install.

Is there a way for me to restart DNN from the database?

Another hint or suggestion?

Chris