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.

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

[bug]: HeadObject operation: Bad Request while uploading any image or artefact to issues #4975

Open
1 task done
ashishlead opened this issue Jul 1, 2024 · 1 comment
Open
1 task done
Assignees
Labels
🐛bug Something isn't working

Comments

@ashishlead
Copy link

ashishlead commented Jul 1, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

Have configured plane over S3 using the steps mentioned here

But while uploading any image or artefact to issue, getting below errror:

api-1  | An error occurred (400) when calling the HeadObject operation: Bad Request
api-1  | ERROR 2024-06-18 12:26:24,205 exception_logger 25 273656705968456 An error occurred (400) when calling the HeadObject operation: Bad Request
api-1  | ERROR 2024-06-18 12:26:24,212 log 25 273656626534728 Internal Server Error: /api/workspaces/test-workspace/projects/d9398df5-8455-4b06-8f4b-aba3615c8afe/issues/c0c5aa71-43de-4ff0-8964-4e6c5772ea0e/issue-attachments/

Steps to reproduce

  1. Configure plane using steps here, https://docs.plane.so/self-hosting/methods/docker-compose
  2. Configure S3 as below:
# DATA STORE SETTINGS
USE_MINIO=0
AWS_REGION=ap-south-1
AWS_ACCESS_KEY_ID=xxxxx
AWS_SECRET_ACCESS_KEY=xxxxx
AWS_S3_ENDPOINT_URL=https://xxxxxx.ap-south-1.amazonaws.com/
AWS_S3_BUCKET_NAME=xxxx-plane-
MINIO_ROOT_USER=access-key
MINIO_ROOT_PASSWORD=secret-key
BUCKET_NAME=lead-plane-jira
FILE_SIZE_LIMIT=5242880
  1. Open plane.so, and upload any image to any issue to reproduce the bug

Environment

Production

Browser

Google Chrome

Variant

Cloud

Version

v0.21.0

@ashishlead ashishlead added the 🐛bug Something isn't working label Jul 1, 2024
@pablohashescobar
Copy link
Collaborator

@ashishlead, while using S3, the AWS_S3_ENDPOINT_URL is not required and the bucket should be public.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants