-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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]: external s3/minio #1318
Comments
Hi @MyWay, I noticed that you're encountering an issue with the endpoint URL. To resolve this, could you please try prepending |
Hi, i have tried your suggestion, but I'm getting the same error. |
Any update or solution for this. I'm having the same issue. I've even tried minio setup when s3 didn't work thinking there might be some issue with the s3 endpoint url but no luck. Still can't make uploads work, the upload api gives 400 with the message "Something went wrong please try again later", that's it. I guess one good way is to log the actual error in the console or the logger so it would be easier to debug and know where it is failing than just ignoring the error with such a broad exception catch. I'd be happy to open a PR regarding the same |
Maybe this is helpful: I had the same problem and debugging was pretty hard. It turned out, that my self hosted minio setup had TLS verification enabled. Those were custom signed TLS certificates and plane was not able to verify the certificate correctly. I completely disable the minio TLS setup and configured plane to use plain HTTP. After this I was able to upload assets. |
I have this issue too. I'm using OpenStack / Swift and I just cannot get anything to upload. In the browser:
My env:
I'm not even sure how to diagnose this, there's nothing helpful at all in the logs. |
A small update, issue not fully fixed however. In my Openstack case changing |
I solved it. My situation is more like django-storages issue.
|
Hey @MyWay, can you check by upgrading to the latest version. This issue should be fixed now. Let us know if you are still facing this issue. |
How should I configure it for an alternative s3 in the latest version? Because upload is working, I can see the file in the bucket, but then the url generated by plane is pointing to my plane instance, so maybe I'm missing some setting. |
You can turn the |
I did set it at 0, the file is uploaded, the filename is correct, but the url is mydomain.ext/mybucketname instead of my external s3 compatible service. |
Oh okay @MyWay, can you also remove the |
If I do won't it use Amazon s3? 🤔 |
It will be still using Amazon S3 only. |
But I'd like to use my s3 compatible provider. |
Oh okay currently Plane only supports S3 and Minio what storage are you using @MyWay ? |
I see, that's the issue with my instance then. I have tried both wasabi and synology, currently on synology. Apparently only missing thing is to generate the correct url using AWS_S3_ENDPOINT_URL. |
@MyWay, you may have to also update the |
You mean I should rewrite urls to reflect my s3 instance, instead of expecting plane to do it? |
You may have to do some changes the current plane setup either connects with S3 or minio for fetching assets for other services you may have to change the configuration a bit to make it work. |
I see. Since all of them implement the same API, do you plan to add support to any of the s3 services? |
Please see #3278 for using custom s3 endpoints |
It's still not working for custom s3 endpoints from what I see. |
Couldn't upload files to AWS S3, I am using the script to run it on a linux server with docker. DATA STORE SETTINGSUSE_MINIO=0 Is there some other change we have to make to enable it to upload to S3. Getting the following error from plane-app-api-1 /api/workspaces/internal/file-assets/ HTTP/1.0" 400 |
I facing same issue when setup default minio. Bellow my config
But in UI, i see it call api Please help |
This issue will be resolved when you update to the latest version of Plane. |
I'm already using latest stable, which version you are referring exactly? |
Is there an existing issue for this?
Current behavior
When I upload the logo, the loader is stuck, while on the console I get: "Something went wrong please try again later".
Steps to reproduce
Couldn't find any useful info neither on the docs, nor here among the issues.
Browser
Google Chrome
Version
Self-hosted
The text was updated successfully, but these errors were encountered: