question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cloudflare R2 error

See original GitHub issue

Describe the bug I’m getting the following errors when using Cloudflare R2; 2022/12/11 16:15:46 [error] 64#64: *1 SSL_do_handshake() failed (SSL: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:SSL alert number 40) while SSL handshaking to upstream 2022/12/11 16:15:46 [warn] 64#64: *1 upstream server temporarily disabled while SSL handshaking to upstream

I can fix the errors and it works fine if I add the following line to default.conf (inside location @s3): proxy_ssl_server_name on; and “hardcoding” my R2 domain in proxy pass: proxy_pass https://abcdefghijklmnopqrstuvwxz1234567.r2.cloudflarestorage.com$s3uri; but having to do that everytime I restart the container is a PITA.

Posting this issue so maybe a kind sould can fix it or post a better solution.

Your environment

  • Version of the repo - a specific commit or tag latest-20221104

  • Version of the container used (if downloaded from Docker Hub or Github) ghcr.io/nginxinc/nginx-s3-gateway/nginx-oss-s3-gateway:latest

  • S3 backend implementation you are using (AWS, Ceph, NetApp StorageGrid, etc) Cloudflare R2

  • How you are deploying Docker/Stand-alone, etc Docker

  • NGINX type (OSS/Plus) OSS

  • Authentication method (IAM, IAM with Fargate, IAM with K8S, AWS Credentials, etc) Secret and access keys

Issue Analytics

  • State:closed
  • Created 9 months ago
  • Comments:12

github_iconTop GitHub Comments

1reaction
dekoboncommented, Dec 15, 2022

I got an account on backblaze and debugged the issue. It appears that we need to set proxy_ssl_name in addition to proxy_ssl_server_name. Please try the latest image without any modifications.

0reactions
dekoboncommented, Dec 16, 2022

Fixed by: 8366ab87ff92ca3aa013b018f3445294e2e30a53 c4212dfe772f3bab5e9677d48c30e7efcdad9b0a

Read more comments on GitHub >

github_iconTop Results From Across the Web

Elevated error rate for R2 - Cloudflare Status
Users may see higher than expected rates of HTTP 500 response codes. We have identified the cause of this issue and are working...
Read more >
Cloudflare R2 HTTP/2 Error - Website, Application, Performance
I am uploading large files (about 150Gi) to Cloudflare R2. When downloading with CURL, the download defauls to HTTP/2.
Read more >
Elevated R2 error rates in our North America regions
Investigating - We're experiencing elevated error rates in our North America regions on certain R2 objects.
Read more >
Sometimes R2 response code 500 - Cloudflare Community
I am testing by applying R2 service. The current usage is to upload ... However, too often, a 500 error appears and the...
Read more >
Queues & R2 - Cloudflare Docs
Example of how to use Queues to batch data and store it in an R2 bucket. ... errors in batches and store them...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found