<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SupportSages &#187; Invalid Hostname</title>
	<atom:link href="http://www.supportsages.com/blog/tag/invalid-hostname/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.supportsages.com/blog</link>
	<description>Technical Support and Server Management : Musings in the fox hole.</description>
	<lastBuildDate>Thu, 05 Jan 2012 03:05:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Bad Request (Invalid Hostname) when accessing via IP</title>
		<link>http://www.supportsages.com/blog/2009/12/bad-request-invalid-hostname-when-accessing-via-ip/</link>
		<comments>http://www.supportsages.com/blog/2009/12/bad-request-invalid-hostname-when-accessing-via-ip/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 19:19:57 +0000</pubDate>
		<dc:creator>George</dc:creator>
				<category><![CDATA[IIS]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Bad Request]]></category>
		<category><![CDATA[Invalid Hostname]]></category>

		<guid isPermaLink="false">http://www.supportsages.com/blog/?p=610</guid>
		<description><![CDATA[Customer wanted to have a dedicated IP, but once I change the IP from the plesk control panel, I couldn't get the website when accessed using IP. Instead, it was giving me the plesk control panel's default page. Reason ? Default Website was having the IP as "All Unassigned". Set that to the main IP address. But after that I was getting a new error.

What I could get was "Bad Request (Invalid Hostname)" in bold letters. Here is what I did to fix the same.

Start -> Run -> inetmgr -> Expand the (+) -> Websites -> Right click on the ...]]></description>
			<content:encoded><![CDATA[<p>Customer wanted to have a dedicated IP, but once I change the IP from the plesk control panel, I couldn&#8217;t get the website when accessed using IP. Instead, it was giving me the plesk control panel&#8217;s default page. Reason ? Default Website was having the IP as &#8220;All Unassigned&#8221;. Set that to the main IP address. But after that I was getting a new error.</p>
<p>What I could get was &#8220;Bad Request (Invalid Hostname)&#8221; in bold letters. Here is what I did to fix the same.</p>
<p>Start -> Run -> inetmgr -> Expand the (+) -> Websites -> Right click on the domain name -> Take Properties -> Website -> IP Address (make sure that it has the dedicated IP assigned there) and then click &#8220;Advanced&#8221;</p>
<p><strong>Add/Edit Web Site Identification</strong></p>
<p>IP Address : Choose the dedicated IP from drop down list<br />
TCP/IP Port : 80<br />
Host Header Value : Leave it blank (Important)</p>
<p>Leaving the Host Header Value should fix the issue and fetch the website when accessing it using the IP.</p>
<div class="tweetthis" style="text-align:left;"><p> <a  class="tt" href="http://twitter.com/home/?status=Bad+Request+%28Invalid+Hostname%29+when+accessing+via+IP+http%3A%2F%2Fwww.supportsages.com%2Fblog%2F610" title="Post to Twitter"><img class="nothumb" src="http://www.supportsages.com/blog/wp-content/plugins/tweet-this/icons/en/twitter/tt-twitter3.png" alt="Post to Twitter" /></a> <a  class="tt" href="http://twitter.com/home/?status=Bad+Request+%28Invalid+Hostname%29+when+accessing+via+IP+http%3A%2F%2Fwww.supportsages.com%2Fblog%2F610" title="Post to Twitter">Tweet This Post</a></p></div>]]></content:encoded>
			<wfw:commentRss>http://www.supportsages.com/blog/2009/12/bad-request-invalid-hostname-when-accessing-via-ip/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

