nginx/nginx-s3-gateway

Peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream

Opened this issue · 0 comments

Describe the bug

Connecting to http://127.0.0.1/ I get a 404
Logs indicate:
2025/03/12 13:07:43 [error] 78#78: *2 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream, client: 172.19.0.1, server: , request: "GET / HTTP/1.1", upstream: "https://100.65.0.228:443/?delimiter=%2F", host: "127.0.0.1"

To reproduce

Steps to reproduce the behavior:

  1. Start container with docker-compose
  2. Connect to http://127.0.0.1/
  3. See error

Expected behavior

I expected to see a list of files in my s3 bucket

Your environment

version: "3"

services:
  nginx-s3-gateway:
    image: "ghcr.io/nginxinc/nginx-s3-gateway/nginx-oss-s3-gateway:latest-njs-oss"
    ports:
      - "80:80"
    environment:
      S3_BUCKET_NAME: my_bucket_name
      AWS_ACCESS_KEY_ID: my_aws_access_key_id
      AWS_SECRET_ACCESS_KEY: my_aws_secret_access_key
      S3_SERVER: s3.af-south-1.amazonaws.com
      S3_SERVER_PORT: 443
      S3_SERVER_PROTO: https
      S3_REGION: af-south-1
      S3_STYLE: virtual-v2
      S3_SERVICE: s3
      DEBUG: true
      AWS_SIGS_VERSION: 4
      ALLOW_DIRECTORY_LIST: true
      PROVIDE_INDEX_PAGE: true
      APPEND_SLASH_FOR_POSSIBLE_DIRECTORY: false
      DIRECTORY_LISTING_PATH_PREFIX: ""
      PROXY_CACHE_MAX_SIZE: 10g
      PROXY_CACHE_SLICE_SIZE: "1m"
      PROXY_CACHE_INACTIVE: 60m
      PROXY_CACHE_VALID_OK: 1h
      PROXY_CACHE_VALID_NOTFOUND: 1m