Max retries exceeded with url from bucket

1

When our app gets the image which uploaded to tigris bucket, it return below error:

HTTPSConnectionPool(host=‘fly.storage.tigris.dev’, port=443): Max retries exceeded with url：/mytemp/1728478323_CB56BDFD-D6CA-4251-A5A0-551000EC12B9.jpg (Caused by SSLError(SSLZeroReturnError(6, ‘TLS/SSL connection has been closed (EOF) (_ssl.c:997)’)))

So how to fix this issue, thanks.

2

There is a solution for this issue: SSLError: HTTPSConnectionPool(host='huggingface.co', port=443) · Issue #17611 · huggingface/transformers · GitHub

Please let the trigris team fix this issue ASSP, thanks.

3

Added tigris

4

Hello @terry1

There is no certificate related issue on Tigris TLS configuration. There can be number of other factors playing into it (like tls version support, client cipher support, client network behind proxy etc…) also our TLS setup is in very good state.

To debug further, can you post the output of

curl -v -I https://fly.storage.tigris.dev
5

Hi, @terry1,

In order to help us investigate, can you confirm if the issue is still happening or it has been resolved?

6

This issue is still happening. Not all of the requests are failed. It looks like that it will happen when many request start at the same time to access our bucket.

BTW, Our vercel app use replicate api, and Our ios apps upload user photo to tigris bucket, then pass the photo url to replicate api.

Thanks.

7

Here is the output when I run the curl on my macbook.

curl -v -I https://fly.storage.tigris.dev
* Host fly.storage.tigris.dev:443 was resolved.
* IPv6: 2a09:8280:1::24:a5c5
* IPv4: 149.248.213.147
*   Trying [2a09:8280:1::24:a5c5]:443...
* Connected to fly.storage.tigris.dev (2a09:8280:1::24:a5c5) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=fly.storage.tigris.dev
*  start date: Sep  9 23:24:33 2024 GMT
*  expire date: Dec  8 23:24:32 2024 GMT
*  subjectAltName: host "fly.storage.tigris.dev" matched cert's "fly.storage.tigris.dev"
*  issuer: C=US; O=Let's Encrypt; CN=E5
*  SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://fly.storage.tigris.dev/
* [HTTP/2] [1] [:method: HEAD]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: fly.storage.tigris.dev]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> HEAD / HTTP/2
> Host: fly.storage.tigris.dev
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/2 403
HTTP/2 403
< content-type: application/xml
content-type: application/xml
< server: Tigris OS
server: Tigris OS
< server-timing: total;dur=192
server-timing: total;dur=192
< strict-transport-security: max-age=63072000; includeSubDomains; preload
strict-transport-security: max-age=63072000; includeSubDomains; preload
< x-amz-request-id: 1728515088793507005
x-amz-request-id: 1728515088793507005
< content-length: 223
content-length: 223
< date: Wed, 09 Oct 2024 23:04:48 GMT
date: Wed, 09 Oct 2024 23:04:48 GMT
<

* Connection #0 to host fly.storage.tigris.dev left intact
8

Now, everything is working and no error anymore.

9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.