Mixed content problem

I am running into a weird mixed content related error when serving discourse using a digitalocean droplet:

digitalocean / cloudflare is handling the SSL part, so this is not configured via Discourse or an nginx based reverse proxy. nginx simply forwards incoming requests to the Docker container running Discourse:

server {
        listen 80; listen [::]:80;
        server_name mysite.org;

        location / {
                proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:;
                proxy_set_header Host $http_host;
                proxy_http_version 1.1;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Real-IP $remote_addr;
        }
}

All assets seem to be loaded fine over https, excepts for this 1 file. By entering the app and searching the postgres database I’ve figured out that it is the file /images/discours.png that is causing the problem. I have tried deleting this file and any references to it in the postgres database in an attempt to just avoid loading this image all together, but obviously Discourse re-adds the image when rebuilding the app (at least, I assume it does).

Hopefully someone can give some advice.

Is that a default site logo? Did you try uploading another one to override it?

Is that a default site logo

Yes, it is a file called discourse.png, so I assume it is a default site logo. In the db it always has an id of -6 (uploads table).

Did you try uploading another one to override it?

Yes, also tried that. Then the same problem applies to the custom, uploaded logo.

안녕하세요,

혼합 콘텐츠(mixed content) 문제에 대해 어떤 단서가 있을까요?

해당 게시물의 권장 사항을 따랐는데도 문제가 여전히 지속되고 있습니다!

미리 감사드립니다!

새 탭에서 해당 이미지를 열 수 있는지 확인해 보세요.

어떤 이미지인지 확인한 후, 다시 업로드해 보세요.

기억이 정확하다면, force_https 매개변수를 확인한 후 새 로고를 업로드했습니다.
https://your.domain/admin/site_settings/category/all_results?filter=force_https

완벽하게 작동했습니다! 정말 감사합니다!