I'm definitely getting the same error.

For some reason, all domains on the server had windows authentication turned on, even the DNN portal 0 site which was working correctly. I have tested turning the authentication off for the portal 0 site, and it works fine both ways.

I went to IIS > server > application pools
Clicked on the domain which is the DNN portal 0 site
Stopped it, then waited a minute and started it again.

The domain is delegated correctly from the registrar, and correctly set up at server level. I know this because DotNetNuke was created in a subfolder, not directly in the root of the website. When I go to the new portal website, it is still automatically redirecting to the correct subfolder.

As a temporary workaround, is there any way to preview a DNN site, or must it be viewed within the correct domain name?

just to make sure: you DID configure a single IIS website for all portals within your installation, right?

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

As an experiment, I have created an alias for another domain within DNN's default portal 0. This has also been sucessfully parked within Plesk. When I try to access that alternate domain, I get the same error as with the domain pointed to the portal 2 site. It seems there is some misconfiguration where I cannot access any domain other than the default domain on portal 0.I have another website on the server (non DNN) with extra parked domains that can be accessed with no problems. They were set up the same way within Plesk.