vhost.conf ---> very strange issue!!! Please help

[netconstructor]

Good day all,

I am having a serious issue which is effecting over 200 of my domains which I am HOPING there is a super quick fix for.

In summary, I am running a new server with plesk 9.0 and for each domain on that server I have a custom "vhost.conf" file located of course within the "conf" directory for each applicable domain name.

Each vhost.conf file looks exactly like this:

ProxyRequests Off
ProxyPass / http://www.source-domain-name.com/custom-domain-folder/
ProxyPassReverse / http://www.source-domain-name.com/custom-domain-folder/


Now... I have a different plesk server running plesk 8.6 and have been using this "vhost.conf" file format for the past 3 years without any issues at all (all the way back to plesk 7.5.4).

The problem is that now, with plesk 9.0 each of the domains with such a vhost.conf file keep giving me the following webpage proxy errors notification as listed below... what is really strange though is that it only happen 50% of the time meaning that if I refresh the page the correct target site shows up, if I refresh again, I get the proxy error below... always 50% of the time... very strange.

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.

Reason: Error reading from remote server

Apache/2.2.2 (Fedora) Server at www.eaofirving.com Port 80



Please note that as far as I am aware there is nothing wrong with my proxy entry as I have used this process for over 3 years and yes I have restarted all services naturally to ensure things are correctly integrated.

Also for the person reading this... I don't have any other vhost.conf entries other than what is listed above and no other files in the conf folder.

Does ANYONE have any idea what is going on here or if since plesk 9.0 something has changed???

I am really lost here and have been working on this for over 9 hours without any luck.

Your help is GREATLY appreciated!!!

Chris

 

[rperea]

This is odd because I don't believe that anything has changed in apache from 8.x to 9.0.
As a matter of fact, the exact same apache RPM should still be installed because Plesk doesn't upgrade it.

Here is what I would do. (I hope you have a backup of the conf files from before the upgrade)

Compare the httpd.conf files from the old installation and the now.
/etc/httpd/conf/httpd.conf
See what changes have been made if any.

Compare all the files in /etc/httpd/conf.d/ from the old installation and now.
See what changes / additions have been made if any.

Last of all.
Compare the httpd.include files from the old installation and the now for a domain that is having the problem.
The httpd.include file can be found at:
/var/www/vhosts/<domain_name>/conf/httpd.include.

My guess is that something in the upgrade changed an apache configuration file or two and something in the apache configuration is different. Find what that is and fix it. If you find a difference and don't know how to go about fixing it, post it here and I will see how I can help.

 

[netconstructor]

Domains VHOST.CONF File

Thank you very much for your reply.

I am currently doing the tests you suggested and just got done comparing the domain specific include file.

The only differences I am noticing there is that the server with the working domains shows the following extra line in every <IfModule> statement:

AddType text/plain .php .php5 .php4 .php3 .phtml

I would be fairly sure in assuming this has nothing to do with it correct?

CH

 

[netconstructor]

httpd.conf files

OK - I just reviewed these and I did notice difference but nothing that stands out as being abnormal.

Please seed the attached files.

 

[netconstructor]

conf.d - directory

Again... the new server has a great deal of additional files in the conf.d directory but nothing that is catching my eye as potentially creating a conflict.

Files attached as zip files for review.

 

[rperea]

I took a look at your conf files and couldn't find anything that stands out as being the culprit. Of course, I am not too fluent with apache configuration file syntax.

I think that the fix is some good old fashioned troubleshooting.

1. Backup all your 9.0 conf files.
2. Restore all your 8.x conf files and delete any conf files that were not there before the upgrade. The idea is to put all your apache configs back exactly the way it was before the upgrade.
3. See if it is fixed. If not, then I am dead wrong and it isn't your apache conf files. But if it does work, then start restoring the 9.0 files 1 by 1 until it breaks again. At that point you can post your results.

 

[sbillis]

Just a stab in the dark here, but have you attempted to restart the httpd service. I would from the command line issue a httpd -t first (to check the config files) and if that was successfull I would then stop the httpd service (service httpd stop) and then start the httpd service (service httpd start).

If you still have issues, I would then look in the httpd error logs for pointers.