You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 12, 2018. It is now read-only.
Some time, the application is running but the connexion with it is lost, for an unknown reason (ECONNRESET). It may be reseted only for a single request, or for every following request. So the user get a 504 error, while the application is running.
Maybe could we add to the error page an action to try to restart the application ?
The text was updated successfully, but these errors were encountered:
In fact, this happens when connections between proxy and the application are not closed cleanly. They stay in CLOSE_WAIT state. By default, Node only allows five concurrent connections to the same origin, so when we reach this limit, the proxy become unable to communicate with the application, and the only solution seems to be to restart the proxy (restarting the application itself seems useless).
Some time, the application is running but the connexion with it is lost, for an unknown reason (
ECONNRESET
). It may be reseted only for a single request, or for every following request. So the user get a 504 error, while the application is running.Maybe could we add to the error page an action to try to restart the application ?
The text was updated successfully, but these errors were encountered: