Set proxy timeout

Test environment - Zimbra Network 7.2.0

Getting Gateway 504 errors.

Trying to modify the proxy_read_timeout and the proxy_send_timeout which are showing 0 in nginx.conf.web Where does one change the variables
of web.upstream.read.timeout and web.upstream.send.timeout

# Set proxy timeout
proxy_read_timeout ${web.upstream.read.timeout};
proxy_send_timeout ${web.upstream.send.timeout};

found in the nginx.conf.web.template?

I modified them manually by removing the ${} part and putting an actual number it its place. Still would really like to know where the "web.upstream.read/send.timeout" variable pulls its data.

Hi,
these values are in zimbra configuration. You can see them with this command (with zimbra user) :
zmprov gacf |grep -i timeout

Exact values are :
zimbraReverseProxyUpstreamReadTimeout: 60s
zimbraReverseProxyUpstreamSendTimeout: 60s

Thank you for the response. Those two variables do not appear in my zimbra configuration. I even had deleted my proxy server and reinstalled it and still they do not appear. Going to try to manually force those two settings and see what happens.

Quote:

---

Originally Posted by sae65

Those two variables do not appear in my zimbra configuration.

---

You need to upgrade to a more recent version of ZCS.

My test system is at 7.2.0 version of ZCS. Those variables do not appear..

Quote:

---

Originally Posted by sae65

My test system is at 7.2.0 version of ZCS. Those variables do not appear..

---

Perhaps it would be an idea if you give a description of what your configuration actually is. FWIW, those settings appear on my 7.2 server.

$ zmprov gacf |grep -i timeout

zimbraDataSourceConnectTimeout: 30
zimbraDataSourceReadTimeout: 60
zimbraMemcachedClientTimeoutMillis: 10000
zimbraReverseProxyCacheFetchTimeout: 3s
zimbraReverseProxyConnectTimeout: 120000ms
zimbraReverseProxyInactivityTimeout: 1h
zimbraReverseProxyRouteLookupTimeout: 15s
zimbraReverseProxyRouteLookupTimeoutCache: 60s
zimbraSmtpTimeout: 60

Misc data: My 7.2.0 imapproxy worked just fine until I had to rename my test server. That is when I noticed that the fields I mentioned in my first post were set to 0. That did not seem correct and I started looking around for where those fields were populated. Sadly I can not say with any authority what the nginx.conf.web looked like before I performed the name change for that server and zimbra services. I was just disappointed when I removed my imapproxy server and reinstalled it that it still was not working. As mentioned in the first posting I did get it to work by modifying the template to reflect a timeout # for those two variables.