mod_proxy / rewrite rules

Hi all,

I'm trying to test the mod_proxy stuff here. My goal is to have a XP server running apache behind my linux box and then if the URL has /app in it, it will pull from the xp server for my dynamic content applications I'm writing.

The reason for this is the engine that I'm using has more features and is more powerful on the windows side vs the linux side.

So in ISPconfig for my site, as a test, I added the following to the apache directives area;
======================================

ProxyRequests Off

<Proxy *>
Order deny,allow
Allow from all
</Proxy>

ProxyPass /app http://192.168.11.1
ProxyPassReverse /app http://192.168.11.1

=======================================

However, after a save and check again, I get 'NOT SUPPORT' messages with my stuff commented out. So my question is, how do I accomplish this?

Thanks,
Ken

PS. I'm basically sending it to my router website as a test.

 

Is mod_proxy enabled in your Apache configuration?

 

Hi Falko,

Thanks for replying. Doh! No I didn't have it enabled. I issued a a2enmod proxy which appears to be the mod_proxy.so module.

After enabling it, it still did not work, so I decided to try some different settings. By using the Directory directive. Still no joy.

Any thoughts?

Thanks,
Ken

 

As you are on a local LAN (and probably not direct Internet link), you could try

Code:

ProxyRequests On

 

Thanks Martin. . . nope, didn't work.

======== edit ===============

Hi all,

Looks like the problem is that my ISPconfig is not updating the Vhosts file. Any reason why it would stop writing to the file??

Thanks,
Ken

 

Thanks till. Still no go on getting ISPConfig to update the vhosts file.

How can I "Force" ISPConfig to rewrite the entire file?

Thanks,
Ken

 

Hi Till,

Sadly there is no "latest file with a date appended to it" available to rename to Vhosts_ispconfig.conf.

Ken

 

Here ya go,

Thanks,
Ken

 

I made a change to one of my sites optional apache directives by just putting in a comment line and saved it. Here is the results in the log;

I noticed that its trying to reload httpd.. shouldn't that be apache2?

Should I put a symlink to apache2 or do we need to investigate further?

Oh also, the comment I made in ISPConfig did not show up in the actual vhosts file.

Thanks,
Ken

 

Which distribution are you using? What's the output of

Code:

ls -la /etc/init.d/

?

 

running The Perfect Setup: Debian Sarge 3.1 and just upgraded to ISPconfig 2.2.9 a week or two ago.

THanks,
Ken

 

Does it say apache2 or httpd in the isp_server table in the ISPConfig database? If it's httpd, either change it to apache2 or create a symlink /etc/init.d/httpd to /etc/init.d/apache2.

 

I created a symlink after I made the post the other day.

For whatever reason its still not updating the vhosts file and I just found out the other day that the SSL is not working on the system either. The ports.conf has 443 in it and I've got the 443 virtual host definition for the same domain name in the vhosts.

thanks,
Ken

 

If you have an error, the vhosts file is not updated and ISPConfig falls back to the previous (working) version, leaving behind a vhosts file with a date/time stamp attached.

To see what's wrong, stop apache2, switch the configfiles vhosts with vhosts_datetime and test with httpd -t. You'll then get to see where your error is.

 

Thanks Martin. Sadly, there is no Vhosts_ispconfig.datetimestamp file being generated by ISPConfig as I mention earlier. I have copied the current vhosts to the format needed by the httpd check, and it comes back with a Syntax OK.

Thanks,
Ken

 

Hi all,

I setup another debian/ispconfig box and created a virtual host on it. I then used the Vhosts_ispconfig.conf for that box as a template and recreated all the entries on my original box. There were huge differences and I'm not sure if it was because I'd upgraded the original from 2.2.6 to 2.2.9 or what, however, I put the new vhosts in place and restarted apache. Made a change in ISPconfig and nothing happened. And amazingly my ssl is still not working on the virtual server I have it turned on for.

I'm going to reinstall ISPConfig and see what happens.

Thanks,
Ken