Welcome to WebmasterWorld Guest from

Forum Moderators: Ocean10000 & incrediBILL & phranque

Message Too Old, No Replies

I've got the virtual hosting blues

2:56 am on Sep 27, 2008 (gmt 0)

New User

5+ Year Member

joined:Feb 23, 2008
posts: 3
votes: 0

I've been working on this all day, and I still can't get virtual hosting to work right. I could really use someones advice.

What I have are two websites that I want to run, the first one called blogscott.org, and the other one without a domain name (we'll call it private.org)

I want both of these sites to be publicly accessible. I have a linksys router that I have to protect my computer. For now, I am only interested in getting blogscott.org to work, and then I'll get the private.org to work. As it is now, I can access the site via www.blogscott.org:85, but not via www.blogscott.org (I get a http error 404).

Here is the http.conf of most interest:

ServerName www.blogscott.org
DocumentRoot "c:\wamp\www"
Listen *:85
NameVirtualHost *:85

<VirtualHost *:85>
ServerName localhost
DocumentRoot /wamp/www
<Directory />
Options FollowSymLinks
AllowOverride All

<VirtualHost *:85>
ServerName www.blogscott.org
DocumentRoot c:/wamp/www/blogscott

<Directory />
Options Indexes FollowSymLinks MultiViews
AllowOverride all
Order allow,deny
Allow from all


<VirtualHost *:85>
ServerName private
DocumentRoot c:/wamp/www/private


My windows host file is as follows:
::1 localhost localhost www.blogscott.org private

I use zoneedit to do a webforward from www.blogscott.org to www.blogscott.org:85. I also use zoneedit for the dns stuff too.

I hope that all makes sense.. can anyone spot the problem?
To summarize, going to www.blogscott.org should work, but does not because of a HTTP 404 error. However, www.blogscott.org:85 does work.

Thanks in advance..

3:15 am on Sept 27, 2008 (gmt 0)

Preferred Member

10+ Year Member

joined:July 16, 2001
votes: 0

If you're doing this from your house, the 404 may not be coming from your apache. (ISPs tend to block port 80 inbound, in the name of keeping down *bad* sights, but mainly to keep their bandwidth usage low.)

Check your logs. You should find a line added each time for the port 85. Try changing all the port 85's to port 86. If port 86 works, but port 80 does not, see if you're getting the 404's in your logs.

You might cheat by setting up a redirect/forward/(varies by provider) with your dns host or registrar. This would allow your site to appear to be example.org, but actually be example.org:85 in a frame.


Join The Conversation

Moderators and Top Contributors

Hot Threads This Week

Featured Threads

Free SEO Tools

Hire Expert Members