mirror of
https://github.com/flyimg/flyimg.git
synced 2026-04-25 09:45:50 +03:00
[GH-ISSUE #493] S3 not working #181
Labels
No labels
Docs
Docs
Docs
Security
UnitTest
bug
dependencies
duplicate
enhancement
enhancement
enhancement
hacktoberfest
help wanted
invalid
pull-request
question
stale
version 1
version 2
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/flyimg#181
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @francescor on GitHub (Sep 8, 2024).
Original GitHub issue: https://github.com/flyimg/flyimg/issues/493
Originally assigned to: @sadok-f on GitHub.
Describe the bug
unable to use s3: nothing arrive in the bucket
Environment setup:
image: flyimg/flyimg:1.4.7Additional context
error logs
@sadok-f commented on GitHub (Sep 9, 2024):
Hi @francescor
thank you for opening this issue.
I didn't find any problem with the S3 storage, I've tested it several times and it's working as expected.
from your logs, I think you're missing the bucket_name:
Can you share your parameters.yml s3 config section:
Please remove the access_id and secret_key values.
thanks
@francescor commented on GitHub (Sep 9, 2024):
yes, I saw that, but the bucket name is there :)
access key are fine since I see the access in the log
@francescor commented on GitHub (Sep 9, 2024):
aws policy
with the above policy in my aws cli I can correcly list content of the bucket and add/remove items
@francescor commented on GitHub (Sep 9, 2024):
I replaced double quotes with single, just in case, no changes
You can test it yourself now https://flyimg-test.boat.opencontent.io/upload/w_300/https://raw.githubusercontent.com/flyimg/graphic-assets/master/logo/raster/flyimg-logo-rgb.png
another error with https://flyimg-test.boat.opencontent.io/upload/w_300/https://wallpapercave.com/wp/WY4oW5x.jpg
@sadok-f commented on GitHub (Sep 9, 2024):
for my testing, even with a large image size I was able to store the images in s3 successfully.
@francescor do you have another server in front of Flyimg?
even with small image size, your test instance failed to save it in s3:
https://flyimg-test.boat.opencontent.io/upload/w_200,q_5,rf_1/https://wallpapercave.com/wp/WY4oW5x.jpg
@sadok-f commented on GitHub (Sep 9, 2024):
can you check your Cross-origin resource sharing (CORS) in your bucket permission section?
@francescor commented on GitHub (Sep 9, 2024):
I was exactly there :)
What are the requirement for the S3 bucket? it could be it was created correctly time ago when we first (unsuccessfully) tested s3, and then closed up for security
(the
Cross-origin resource sharing (CORS)is empty)@sadok-f commented on GitHub (Sep 9, 2024):
There's no requirement for the S3 bucket, as I said I created a new bucket and tested a couple of images successfully without issue.
@francescor commented on GitHub (Sep 9, 2024):
so the bucket does not need to be accessible by the public, only restricted access to it with the credentials, ok?
ah, there still was a CORS in our side active, sorry, you were right: I've removed it now
@francescor commented on GitHub (Sep 9, 2024):
uh, I've created a new bucket, and not it works
@francescor commented on GitHub (Sep 9, 2024):
found the bug: if the bucket name include dots (
.) the error shows upcancellamiworkscancellami.flyimg.opencontent.itdoes not work@francescor commented on GitHub (Sep 9, 2024):
I've just double checked it, and that appears to be the issue
@sadok-f commented on GitHub (Sep 9, 2024):
I see, thanks let me investigate it then.
@sadok-f commented on GitHub (Sep 9, 2024):
@francescor I think I found the issue with the S3 storage provider, please wait until the build of the new version is finished and give it a try (1.4.8)
@francescor commented on GitHub (Sep 9, 2024):
yes, it works! thank you so much!
(page title works, too!)