La subida del sistema no utiliza la URL de CDN de S3

Soporte Instalación
,
1

Versión v2.2.0.beta3 +153

Estoy utilizando MinIO como puerta de enlace S3 interna. Sin embargo, al subir una imagen, no se utiliza la URL de la CDN.

Por ejemplo, al subir un avatar, se utiliza una IP interna en lugar de la URL de la CDN. Esto hace que el avatar no se pueda mostrar.

2

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?

3

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.

4

So you’ve followed the official guide for configuring Minio with Discourse?

How does your setup differ?

5

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.

6

Capture
Capture.PNG1034×823 87.5 KB

Here is my config.

Actually, the preview also link to IP instead of CDN. Only the image being in post (original and optimized) are using CDN url.

7

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.

8

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

9

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.

10

Así que sigo confundido aquí… incluso con mi URL de CloudFront en “s3 cdn url”, todas las imágenes cargadas (en la vista previa o no) están usando la URL s3.dualstack y no mi URL de CloudFront/CDN.

¿Qué me estoy perdiendo?

Estas son mis configuraciones:

Screen_Shot_2019-10-08_at_12_11_10_PM
Screen_Shot_2019-10-08_at_12_11_10_PM800×1162 165 KB
Texto preformateado

Esto parece un error, no una característica, ya que requiere que tu bucket de S3 tenga ACLs públicas. Parece que ya se reportó aquí hace años, pero no se ha solucionado: S3 CDN URL ignored when uploading into posts