The private_ip:5044 is closing the connection before completing the request.
You should check the log in the upstream server for why it is doing this.
Perhaps a security module or something that drop connection immediately etc
On Fri, May 21, 2021 at 2:46 PM Mauro Tridici wrote:
>
> Dear Users,
> Is there a reason why you need nginx "cache" instead of just storing the
files statically?
I don't have a big enough disk to store *all* user uploaded files
accumulated over the years. So I need some way to manage a pool of space to
store hot uploads.
> One way would be instead of using the ca
Hello!
On Thu, May 20, 2021 at 10:13:01PM -0400, mbrother wrote:
> Thank you for your answer. As you know, nginx does not send Auth command to
> backend server, so there's no way for the backend to know if the sender
> matches the authenticated account. I tried proxy_smtp_auth config but nginx
>
> One option is to keep a copy of the file on disk (outside of the nginx
cache). Then use something like try_files to read it, and have that response
be cached by nginx. But then I end up with 2 of the files on disk (one in my
try_files directory, and one in the nginx cache). I also need to manuall
Dear Users,
I’m noticing a these error messages in /var/log/nginx/error.log.
021/05/21 10:57:25 [error] 21145#0: *7 recv() failed (104: Connection reset by
peer) while proxying connection, client: public_ip, server: 0.0.0.0:5044,
upstream: "private_ip:5044", bytes from/to client:321/7709, byte
