nginx-proxy-manager
nginx-proxy-manager copied to clipboard
NginxProxyManager
Custom Timeout
The default timeout of Proxy Hosts seems to be 1 Minute, wich is pretty short, so i would like to change the timeout without having to use a Custom Nginx Configuration.
Describe the solution you'd like A input field in the Web Interface to change the timeout per Proxy Host. It should probably set following nginx configuration parameters:
- proxy_connect_timeout
- proxy_send_timeout
- proxy_read_timeout
- send_timeout
Additional context
Def need this.. so many things i reverse proxy need a much longer timeout.. Anything to do with Docker usually takes more than a minute to build a container and NPM causes it to bail out.
Maybe i will do a PR for this Feature at some point, but i currently don't have enough time
The "workaround" is: just add the parameter you want to change to the advanced config field. If you want to change the proxy timeout, set the corresponding proxy timeout variables.
I am using the following line of advanced custom config to prevent console disconnects in Portainer:
proxy_read_timeout 30m;
The "workaround" is: just add the parameter you want to change to the advanced config field. If you want to change the proxy timeout, set the corresponding proxy timeout variables.
I am using the following line of advanced custom config to prevent console disconnects in Portainer:
proxy_read_timeout 30m;
Did this actually work for you? I added the above, and I still timeout...
The "workaround" is: just add the parameter you want to change to the advanced config field. If you want to change the proxy timeout, set the corresponding proxy timeout variables. I am using the following line of advanced custom config to prevent console disconnects in Portainer:
proxy_read_timeout 30m;Did this actually work for you? I added the above, and I still timeout...
I think it did. I have not had any timeouts since, but i cannot confirm if this configuration fixed it or something else.
@mriksman It worked for me as well, with timeouts in the portainer console. Maybe whatever app you proxy has some internal timeouts which expire independent of whether the proxy connection is kept open?
Oh and @JonathanTreffler, why is it exactly that you want this feature without the custom nginx configuration? That's exactly what the custom config is for.
Portainer. Google pointed me to proxy_read_timeout and people said it was not a Portainer issue, but a Reverse Proxy issue. Not sure what MY issue is then!
Oh and @JonathanTreffler, why is it exactly that you want this feature without the custom nginx configuration? That's exactly what the custom config is for.
It seems very easy to implement and requires no duckduckgo-ing :)
Update: Portainer is adhering to the setting. Sort of...
proxy_read_timeout 0; causes a 504 error; times out before the console can load.
proxy_read_timeout 10; killed the Portainer websocket console after 10 seconds.
proxy_read_timeout 3600; timed out after 100 seconds (1 min 40 seconds)...
...So somewhere there is a 100s timeout taking precedence....??
The "workaround" is: just add the parameter you want to change to the advanced config field. If you want to change the proxy timeout, set the corresponding proxy timeout variables.
I am using the following line of advanced custom config to prevent console disconnects in Portainer:
proxy_read_timeout 30m;
How to do it? Can tutorial for me do this? tks
