Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Bad Request - Invalid HostnameBad Request - Invalid Hostname
Previous
 
Next
New Post
7/19/2012 1:52 PM
 
This is a newly installed DotNetNuke site on a VM.  I can access the site locally when I am logged into the VM and navigate to the the site, but every time I attempt to access it from my physical computer or some other remote location, I get the message stating Bad Request - Invalid Hostname. 

The only thing I can think of is that the Host URL is http://www.dotnetnuke.com.  I used this as the default setting.  Any information is appreciated.
 
New Post
7/19/2012 3:25 PM
 

Under Host->Site Management you need to set up an alias for the site. You probably have to set it up to point to either your VMs IP or computer name.

 
New Post
7/20/2012 1:41 PM
 

Mike: Thank you for your idea. 

Our group attempted a number of other ideas as well and still could not get dotnetnuke to work properly.  Eventually I just restored the server to a previous state and tried a fresh installation without success.  Unfortunately, I will have to eliminate dotnetnuke from the list of CMS products that are being evaluated.  It is too bad since I was hoping for an easier integration between dotnetnuke and our existing Windows Server environment. 

 
New Post
7/20/2012 2:02 PM
 

Bad Request - Invalid Hostname is actually an IIS response, isn't it? Are you able to navigate to ANY IIS website? BEFORE you install DotNetNuke, see if you can properly reach a "hello world" HTML page to ensure that IIS and your routing is setup correctly. This sounds much more like a simple routing problem.

Cheers.


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Bad Request - Invalid HostnameBad Request - Invalid Hostname


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out