Apache Friends Support Forum

Hello Everyone,

I'm trying to set up xampp to work with multiple virtual hosts and I'm having trouble. My 'default' vhost works fine, however my second vhost reports the following:

`Failed to forward the request to the web server at burningones.local:80. This may be due to a firewall configuration error or a DNS failure.`

`apache -S` reports nothing wrong with the vhost configuration, and I currently have the following in my httpd-vhosts.conf file.

`NameVirtualHost 127.0.0.1

<VirtualHost 127.0.0.1:80>
DocumentRoot /xampp/htdocs
ServerName localhost
ServerAlias www.localhost
</VirtualHost>

<VirtualHost 127.0.0.1:80>
DocumentRoot /xampp/htdocs/burningones.com/implementation
ServerName burningones.local
ServerAlias www.burningones.local
</VirtualHost>

<Directory "C:\xampp\htdocs\burningones.com\implementation">
Order allow,deny
allow from all
</Directory>`

burningones.local is set to resolve to 127.0.0.1 in my `etc/hosts` file.

Any help would be greatly appreciated. This is completely out of my depth.

Failed to forward the request to the web server

Which software is producing this message?

It appears to be XAMPP that is generating that message (apache), but I don't know how to confirm that.

but I don't know how to confirm that.

If this is an error message from Apache, you can see this in the "error.log".

(BTW: Never seen this message in the Apache source code...)

Is this the complete text from the browser? It's looks more a message from a proxy server.

Umm... Ok... Thank you for your help, I've changed _nothing_, and it now works...

I had restarted the servers many times, but I just tried it again after awhile and the dns redirect works.

Wish I knew what went wrong, but at least it's working now...

Thanks again!

OK... Actually found something possibly useful. The VHost works _great_ in Firefox, but in Chrome (The browser I've been using to try to view my local install.) I still get that error. I have no idea what could be causing this, but I think it's safe to say that it's an issue with Chrome, not with apache or XAMPP or anything like that.

Perhaps smarter people could analyze that little tid bit of info.