Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: Not able to configure Digital Ocean spaces as S3 storage #4806

Open
VipinGoyal opened this issue Jan 12, 2025 · 0 comments
Open

[Bug]: Not able to configure Digital Ocean spaces as S3 storage #4806

VipinGoyal opened this issue Jan 12, 2025 · 0 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@VipinGoyal
Copy link

VipinGoyal commented Jan 12, 2025 •
edited
Loading

Error Message and Logs

Not able to configure Digital Ocean space as S3 storage, though AWS S3 is working but Digital Ocean is not.

Im getting this error while saving details with this endpoint i.e. https://nyc3.digitaloceanspaces.com

Unable to list contents for '', shallow listing

Reason: Error executing "ListObjectsV2" on "https://nyc3.digitaloceanspaces.com/?list-type=2&prefix=&delimiter=%2F"; AWS HTTP error: Client error: `GET https://nyc3.digitaloceanspaces.com/?list-type=2&prefix=&delimiter=%2F` resulted in a `403 Forbidden` response:
<Error><Code>AccessDenied</Code><Message>Access Denied.</Message><Resource>/</Resource><RequestId>not available</Request (truncated...)
 AccessDenied (client): Access Denied. - <Error><Code>AccessDenied</Code><Message>Access Denied.</Message><Resource>/</Resource><RequestId>not available</RequestId></Error>

Also, tried with both region as us-east-1 and nyc3 in endpoint as well
When I remove region from endpoint or add bucket name additionally, I'm able to save the configuration but while saving backup Im getting this error i.e.

So, with https://digitaloceanspaces.com, Im getting this error

mc: <ERROR> Unable to initialize new alias from the provided credentials. <html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>cloudflare</center>
</body>
</html>.

and with this endpoint, https://.nyc3.digitaloceanspaces.com Im getting this error where is actual bucket name

mc: <ERROR> Unable to initialize new alias from the provided credentials. The specified key does not exist.

I've added nyc3 as a region in endpoint as per comment here #2615 and tried with both region i.e. us-east-1 and nyc3 as mentioed here client, but Im not able to confgure digitalocean s3 compatible storage, when I checked with ChatGpt, this is what it said

  1. Check for Signature Version or Path Style Options
    Some S3 libraries (or wrappers used by Coolify) need additional parameters to talk nicely to DO Spaces:

Signature Version: DO Spaces generally uses Signature Version 4 (v4). If the library is forcing v2 or if signature mismatch occurs, you’ll get a 403.
Path-Style vs Virtual-Host–Style: Many DO Spaces setups require virtual-host–style (i.e., bucket name as a subdomain). But some tools only work with path-style unless configured. If your library is building a URL like https://nyc3.digitaloceanspaces.com/my-bucket/..., it may fail if Spaces is expecting https://my-bucket.nyc3.digitaloceanspaces.com/..., or vice versa.
In short, if there’s a toggle in Coolify to “use path style endpoint” or “use virtual host style”, try flipping it.

Steps to Reproduce

  1. Im getting this error while saving details with this endpoint i.e. https://nyc3.digitaloceanspaces.com in S3 storgae option.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.380

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

No response
@VipinGoyal VipinGoyal added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Jan 12, 2025
@VipinGoyal VipinGoyal changed the title [Bug]: [Bug]: Not able to configure Digital Ocean spaces as S3 storage Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@VipinGoyal