server 5 proxy timeout settings

Moving on to Server 5.3 and this has been changed again. The apache_serviceproxy_customsites.conf just contains some Use statements that refer back to a <Macro section in apache_serviceproxy.conf. Open /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf and look for the <Macro section for virtual hosts on port 80 and make your ProxyPass changes there.

I've now decided that the easiest way to avoid having to make changes with every new version of Server, is to run the website on a different port, say 81. By running on a different port the website isn't using the proxy server at all. If any changes are required to the configuration, these can be put in a new .conf file and then you can define a very simple webapp. See the man pages for webapp.plist. If you are accessing the site from outside your firewall, you need to forward your new port to the MacOS server.

thanks

Many thanks for your post.

I entounter the same error, but your solution doesn't work for me (I think) because we are delegating a subdomain to another machine/IP.

I tried to add the timeout also to the corresponding .conf file without success:

/Library/Server/Web/Config/apache2/sites/0000_127.0.0.1_34580_subdomain.domain. com.conf

Maybe someone a solution for that? Many thanks in advance!

OS X El Capitan (10.11.1), Server 5.0.15

Solved it!

my current setting contains also a keepalive, ttl and ProxyTimeout parameter (might be redundant):

ProxyPass / http://subdomain.domain.com/ timeout=300 keepalive=On ttl=300 ProxyTimeout=300

added in

/library/server/Web/Config/proxy/apache_serviceproxy.conf

as well as

/Library/Server/Web/Config/apache2/sites/0000_127.0.0.1_34580_subdomain.domain.c om.conf

i'm sorry, the parameter 'ProxyTimeout=300' is wrong and leads to an error.

Added the following to /library/server/Web/Config/proxy/apache_serviceproxy.conf into the virtual hosts *80 sections:

ProxyPass / http://localhost/ timeout=900

After rebooting the server websites were not responding, which lead me to the conclusion that the config was in conflict witht something and preventing Apache webserver from launching.

Reverted the changes for now... Still trying to find a solution to scripts timing out. I have plenty of cron jobs launching lengthy scripts that take 5-10 minutes to fetch data from the Internet...

Ok, I have found the solution. It is enough to simply add one line to the config file.

1. sudo nano /library/server/Web/Config/proxy/apache_serviceproxy.conf

2. Find: <VirtualHost *:80>

3. Add on a new line below: ProxyTimeout 300

4. Find: <VirtualHost *:443>

5. Add on a new line below: ProxyTimeout 300

Save and restart server. Fixed the 502 proxy error for me!

I'll give this a go now, thank you.

I feel those settings certainly helped. Profile Manager stays up longer now before I get the error message. Would increasing the ProxyTimeout value to something higher than 300 possibly help me further?

Many thanks for the info Bunnyfu - profile manager has been driving me nuts for months!

If your script takes more than 300 seconds, definitely increase the timeout. My scripts completely stopped timing out, because they are done in 3-4 minutes. I dont know how the server will react if you give it an insane timeout like 9999, but its worth a shot. 🙂 Its also worth checking the mod_proxy documentation to see if you can jus set the timeout to 0 for infinitey.

I've set to 400 for now and see what happens. Shame profile manager is so flaky on server 5 - lets hope Apple patch this and get things sorted!

400 seemed to make PM slow down too much (unless this was a coincidence with another problem). I now have the setting at 200 and although I get the odd crash, its a LOT less frequent than before.

Thanks again for the info - certainly helped!

Just to update, I now have the timeout setting at 200 and although PM is a little slower, its DEFINITELY more stable than before.

I have also disabled APN and Internet Reachability which has lowed the CPU load with the postgres_real service. (I dont believe we need internet reachability to be on in our network as we have a NAT rule in place for external comms)

Many thanks to Bunnyfu for the timeout modification which certainly made the biggest difference.

further update - 200 was leading to crashes once our estate got busy. setting currently at 350. slow but more stable 😀