You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we want to use the S3 plugin to store the attachments in a bucket on our MinIO instance. Currently our MinIO is setted up as a single-node. In MinIO I have created a fresh bucket and created an access key with secret for this bucket. In our test environment the access key have all permissions for MinIO. Sadly we receive an error in the log on GuzzleHttp level.
After this, we have tryed to use the public MinIO play instance (https://play.min.io), same error.
Attachment upload shows that it was successful but after we close the dialog the attachment list doesn't contain the uploaded file.
Expected behaviour
Attachment upload successfully stored in S3 bucket or a proper error message is displayed that the upload was not successful. In debug.log we expect more details.
Steps to reproduce
1.) In config.php set the required parameters and restart your container or kanboard instance:
Hi,
we want to use the S3 plugin to store the attachments in a bucket on our MinIO instance. Currently our MinIO is setted up as a single-node. In MinIO I have created a fresh bucket and created an access key with secret for this bucket. In our test environment the access key have all permissions for MinIO. Sadly we receive an error in the log on GuzzleHttp level.
After this, we have tryed to use the public MinIO play instance (https://play.min.io), same error.
I have created a PR for a fix for that: #16
Actual behaviour
Attachment upload shows that it was successful but after we close the dialog the attachment list doesn't contain the uploaded file.
Expected behaviour
Attachment upload successfully stored in S3 bucket or a proper error message is displayed that the upload was not successful. In debug.log we expect more details.
Steps to reproduce
1.) In config.php set the required parameters and restart your container or kanboard instance:
Note, this is the public MinIO play instance, the credentials are available for public usage!
2.) Try to upload an attachment to an existing task
3.) Have a look at stderr or stdout or debug.log (depends on your configuration)
Configuration
The text was updated successfully, but these errors were encountered: