504 gateway timeouts

Wade Girard wade.girard at gmail.com
Fri Jan 5 04:45:15 UTC 2018

I am not sure what is meant by this or what action you are asking me to
take. The settings, when added to nginx conf file on Mac OS server and
nginx reloaded take effect immediately and work as expected, the same
settings when added to nginx conf file on Ubuntu and nginx reloaded have no
effect at all. What steps can I take to have the proxy in nginx honor these
timeouts, or what other settings/actions can I take to make this work?


On Thu, Jan 4, 2018 at 7:46 PM, Zhang Chao <zchao1995 at gmail.com> wrote:

> > The version that is on the ubuntu servers was 1.10.xx. I just updated it
> to
> >
> > nginx version: nginx/1.13.8
> >
> > And I am still having the same issue.
> >
> > How do I "Try to flush out some output early on so that nginx will know
> that Tomcat is alive."
> >
> > The nginx and tomcat connection is working fine for all
> requests/responses that take less t
> Maybe you can flush out the HTTP response headers quickly.
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

Wade Girard
c: 612.363.0902
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20180104/d7768a54/attachment-0001.html>

More information about the nginx mailing list