Skip to content

Getting issue During S3 configuration #3490

Closed

Description

@iamjameel006

@mdp @notpushkin @kylewlacy @AnkushD

USE_MINIO=0
AWS_REGION="eu-west-1"
AWS_ACCESS_KEY_ID="[reducted]"
AWS_SECRET_ACCESS_KEY="[reducted]"
AWS_S3_ENDPOINT_URL="https://bucket-name.region.s3.amazonaws.com/"
AWS_S3_BUCKET_NAME="[reducted]"
FILE_SIZE_LIMIT=52428800

Is there some other change we have to make to enable it to upload to S3. I am not getting any error, but when i upload the image it just load uploading for some time then disappear.

Activity

  1. changed the title [-]Getting 502 Error During S3 configuration[/-] [+]Getting issue During S3 configuration[/+] on Jan 29, 2024
  2. poudelprakash commented on Feb 15, 2024

    @poudelprakash

    @iamjameel006 Your issue is probably realated to #3278

  3. dhruv-nudge commented on Oct 17, 2024

    @dhruv-nudge

    @iamjameel006 were you able to get it working?

  4. poudelprakash commented on Oct 20, 2024

    @poudelprakash

    @dhruv-nudge it is working for me, what is the issue you are facing?

  5. dhruv-nudge commented on Oct 23, 2024

    @dhruv-nudge

    @poudelprakash in the issue-attachment API, I keep getting this error

    {"error":"Something went wrong please try again later"}
    

    When I checked logs, I got this issue

    api-1  | An error occurred (403) when calling the HeadObject operation: Forbidden
    api-1  | ERROR 2024-10-23 12:24:48,729 exception_logger 25 252747202488648 An error occurred (403) when calling the HeadObject operation: Forbidden
    

    I have checked the IAM policies, and bucket permissions, those are correctly configured, but I keep getting this error

  6. leedsjb commented on Nov 3, 2024

    @leedsjb

    Is your S3 bucket public or private? Private buckets are only recently supported.

  7. dhruv-nudge commented on Nov 15, 2024

    @dhruv-nudge

    tried both private and public but didn't work

  8. dhruv-nudge commented on Dec 17, 2024

    @dhruv-nudge

    @leedsjb @poudelprakash any idea what might be the issue?

  9. vihar commented on Nov 1, 2026

    @vihar
    Contributor

    Storage setup has changed a lot since this was filed. Browsers now upload straight to the bucket with presigned URLs, so the bucket needs a CORS rule for your Plane domain, and the IAM user needs get and put access.

    @dhruv-nudge a 403 on HeadObject means the API can't read the object, so check s3:GetObject for that user on the bucket.

    https://developers.plane.so/self-hosting/govern/database-and-storage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions