Version v2.2.0.beta3 +153
I am using minio as a S3 gateway internal. However, when upload a image, it does not using the CDN url.
For example, uploading a avatar and it uses a internal IP instead of cdn url. This make the avatar fail to display.
Does the IP discourse presents as the CDN match the IP you’re using for Minio? Does the public DNS name for Minio have a certificate?
I am using minio on internal upload only. For example, discourse on 192.168.1.5 and minio on 192.168.1.6:9000. When I browse in Chrome, it tries to request 192.168.1.6:9000 which will not work.
I expect it to load from cdn.example.com which like image in post.
So you’ve followed the official guide for configuring Minio with Discourse?
How does your setup differ?
Yes, I followed the guide. It works on images upload in posts but not system upload. For example avatar, logo and icon.
All the images in posts use cdn.example.com but system upload use 192.168.1.6:9000.
This problem seems to happen here as well. If you upload an image, the one you see in preview is discourse-meta.s3.dualstack.us-west-1.amazonaws.com instead of meta-s3-cdn.freetls.fastly.net.
Yeah this is indeed the case, preview does not use CDN, hiding the S3 origin from clients is an unsupported setup atm, longer term I expect even more trouble when we support direct to s3 uploads
I also found out the images uploaded are allowed to view by public. If there are future updates on this, please do not set it if CDN is set. This is because it bypass the bucket policy to enforce all objects must go through CDN.
그래서 여전히 혼란스럽습니다… "s3 cdn url"에 CloudFront URL을 입력해 두었는데도, 업로드된 모든 이미지(미리보기 여부와 관계없이)가 제 CloudFront/CDN URL 대신 s3.dualstack URL을 사용하고 있습니다.
무엇을 놓치고 있는 걸까요?
제 설정은 다음과 같습니다:
Preformatted text
이것은 버그이지 기능이 아닙니다. 왜냐하면 S3 버킷에 공개 ACL을 요구하기 때문입니다. 몇 년 전에 여기에서 보고된 적이 있지만 수정되지 않은 것 같습니다: S3 CDN URL ignored when uploading into posts