Ssl_certificate_key /etc/letsencrypt/live//privkey.pem
Ssl_certificate /etc/letsencrypt/live//fullchain.pem Proxy_set_header X-Forwarded-Proto $scheme Proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for Ssl_protocols TLSv1 TLSv1.1 TLSv1.2 # Dropping SSLv3, ref: POODLE Include /etc/nginx/modules-enabled/*.conf etc/default/minio): MINIO_VOLUMES="/mnt/minio_data/" Wasn't present in RELEASE.T23-50-36Z, is definitely present in RELEASE.T23-57-45Z, may be present to RELEASE.T19-07-09Z.
Execute a request to NGINX to list buckets. Configure NGINX to reverse proxy to MinIO. All subsequent requests then continue to time out. Occasionally (usually after I restart NGINX), a single connection (e.g. NGINX almost always times out when communicating with MinIO. NGINX should be able to communicate with MinIO without timing out. So something must have changed on the MinIO side to cause NGINX to start acting up. I appreciate that the apparently faulty component here is NGINX, however this was working (and has worked since I deployed this last year) up to and include RELEASE.T23-50-36Z. RELEASE.T23-57-45Z: įor all intents and purposes the requests / responses between the two versions appear to be identical. Ĭontent-Security-Policy: block-all-mixed-content I have grabbed some HTTP trace from both versions RELEASE.T23-50-36Z and RELEASE.T23-57-45Z. If I roll back to RELEASE.T23-50-36Z, the issue immediately disappears. I've enabled MINIO_HTTP_TRACE and from looking at the logs, it appears that MinIO is servicing the request from NGINX, but from what I can tell something is then causing NGINX to hang, which eventually causes the client to time out. There is nothing obvious in the changelogs that would indicate what might be causing this. So this is a problem with how NGINX communicates with MinIO that was introduced in either RELEASE.T19-07-09Z or RELEASE.T23-57-45Z. If I remove the reverse proxy and connect directly to MinIO, the issue disappears. Since upgrading to RELEASE.T23-57-45Z, my NGINX reverse proxy almost always times out when servicing connections to MinIO. However, I can replicate this issue using any S3 compliant tool (the examples below were generated using Cyberduck CLI). I currently use MinIO as a target for my Synology NAS's Hyper Backup process. 
Following on from the conversation in #7577, I've upgraded to RELEASE.T23-57-45Z from RELEASE.T23-50-36Z (I can't test if this issue is present in RELEASE.T19-07-09Z due to the issue described in #7577).
0 kommentar(er)
