[GH-ISSUE #98] s3 destination no longer working after update > 0.3.0 #81

New issue

Closed

opened 2026-02-26 21:34:20 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 21:34:20 +03:00

Owner

Originally created by @brunnels on GitHub (Feb 19, 2025).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/98

I updated the base container and my s3 destination is no longer working. The server is a local s3 running on my qnap over https with letsencrypt certs. The same destination works with volsync, authelia, crunchy postgres operator, cloudnative pg, etc...

Here's the error when adding the destination:

error testing destination: failed to test S3 bucket: operation error S3: HeadBucket, exceeded maximum number of attempts, 3, https response error StatusCode: 0, RequestID: , HostID: , request send failed, Head \"qnap-server.local.com:8010\": unsupported protocol scheme \"qnap-server.local.com\"

I thought it might be certs because I had an issue with authelia and my letsencrypt certs so I added the same letsencrypt CA and intermediate cert file that resolved that issue and set the SSL_CERT_FILE env var to the file path. This didn't resolve anything and I get the same error.

The destination works fine with 0.3.0.

Originally created by @brunnels on GitHub (Feb 19, 2025). Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/98 I updated the base container and my s3 destination is no longer working. The server is a local s3 running on my qnap over https with letsencrypt certs. The same destination works with volsync, authelia, crunchy postgres operator, cloudnative pg, etc... Here's the error when adding the destination: ``` error testing destination: failed to test S3 bucket: operation error S3: HeadBucket, exceeded maximum number of attempts, 3, https response error StatusCode: 0, RequestID: , HostID: , request send failed, Head \"qnap-server.local.com:8010\": unsupported protocol scheme \"qnap-server.local.com\" ``` I thought it might be certs because I had an issue with authelia and my letsencrypt certs so I added the same letsencrypt CA and intermediate cert file that resolved that issue and set the `SSL_CERT_FILE` env var to the file path. This didn't resolve anything and I get the same error. The destination works fine with 0.3.0.

kerem closed this issue

2026-02-26 21:34:20 +03:00

kerem commented

2026-02-26 21:34:21 +03:00

Author

Owner

@brunnels commented on GitHub (Feb 19, 2025):

I test image tags 0.4.0 and 0.4.2

@brunnels commented on GitHub (Feb 19, 2025): I test image tags `0.4.0` and `0.4.2`

kerem commented

2026-02-26 21:34:21 +03:00

Author

Owner

@brunnels commented on GitHub (Feb 19, 2025):

Here's my flux kustomization manifest in case that might help answer any other questions you might have. https://github.com/brunnels/talos-cluster/tree/kdev2/kubernetes/apps/management/pgbackweb

@brunnels commented on GitHub (Feb 19, 2025): Here's my flux kustomization manifest in case that might help answer any other questions you might have. https://github.com/brunnels/talos-cluster/tree/kdev2/kubernetes/apps/management/pgbackweb

kerem commented

2026-02-26 21:34:21 +03:00

Author

Owner

@eduardolat commented on GitHub (Feb 19, 2025):

Add http:// or https:// in front of your endpoint and try again

@eduardolat commented on GitHub (Feb 19, 2025): Add http:// or https:// in front of your endpoint and try again

kerem commented

2026-02-26 21:34:21 +03:00

Author

Owner

@brunnels commented on GitHub (Feb 20, 2025):

@eduardolat yes, that fixed it. I could have sworn I tried that though. Thanks for the assistance and for sharing your work!

@brunnels commented on GitHub (Feb 20, 2025): @eduardolat yes, that fixed it. I could have sworn I tried that though. Thanks for the assistance and for sharing your work!

kerem referenced this issue

2026-02-26 21:34:41 +03:00

[PR #81] [MERGED] Refactor components to use NodX library, replacing gomponents referen… #148