I’m not using a proxy, it’s just a straight connection to nginx. If the above wouldn’t be enough to solve you problem, pleaseįollow generic instructions as outlined at if nginx thinks client timed out or so on). Note that setting logging level to ‘info’ may be important in someĬases (e.g. Most simple aproach is to configure oneĪt global level and remove others if any (i.e. Please make sure you have error_log properly configured and youĪre looking at right one. Processes were all still there after the download dies. System had plenty of memory (several hundred MB free) and the worker I checked the usual things: There wasn’t anything in the error log, the Space (or no access to) in proxy_temp_path. Some backend server? In later case most likely reason is out of I’ve had to revert to lighttpd because ofĪre you serving file as static one with nginx, or proxy_pass to On Thu, at 04:34:34PM -0400, nickn wrote:ġ.) What would cause nginx to randomly stop serving large fileĭownloads? When I try to download a 800MB file it stops serving the fileĪfter between 10 and 30 MB.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |