Hello, can someone help to understand why images do not get uploaded but instead showing upload processing? I tried disabling an optimization but it did not help. I am on latest discourse version self hosted, file is PNG 1Mb on air theme. Thanks
1 Like
Hello, can you look at the browser’s console and see if you get any errors when it happens?
1 Like
Very strange stuff, it worked with a different browser Safari, then I switched back to Brave that was giving a problem and it worked now also. All I did it was I restarted my computer.
Although checking Brave console here what is shows below. I am not a programmer so not sure how to make changes to get rid of these warnings. Any help would be appreciated. Thanks!
***45Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure font '<URL>'. This request has been blocked; the content must be served over HTTPS.***
***app.js:239 ℹ️ Discourse v3.5.0.beta2-dev — https://github.com/discourse/discourse/commits/18c8a8ffca — Ember v5.12.0***
***13deprecated.js:61 Deprecation notice: PluginOutlet arguments should now be passed using `@outletArgs=` instead of `@args=` (outlet: category-box-below-each-category) [deprecation id: discourse.plugin-outlet-args]***
***a @ deprecated.js:61***
***site.js:130 âś… Using the new 'glimmer' topic list***
***hamforum.org/:1 Mixed Content: The page at 'https://hamforum.org/' was loaded over HTTPS, but requested an insecure element 'http://hamforum.org/uploads/default/original/1X/011bca162039029c26490fea3769b9d0fde6dd11.webp'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html***
***hamforum.org/:1 Mixed Content: The page at 'https://hamforum.org/' was loaded over HTTPS, but requested an insecure favicon 'http://hamforum.org/uploads/default/optimized/1X/d6407243bedd7a8b0323cffb345cb60750c7f8b8_2_32x32.png'. This request has been blocked; the content must be served over HTTPS.***
***hamforum.org/:1 Mixed Content: The page at 'https://hamforum.org/' was loaded over HTTPS, but requested an insecure element 'http://hamforum.org/uploads/default/optimized/1X/d5f25e2f27014348ef24a5b9e927a7641c1c5dea_2_512x512.webp'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html***
***4:1 Mixed Content: The page at 'https://hamforum.org/c/general/4' was loaded over HTTPS, but requested an insecure favicon 'http://hamforum.org/uploads/default/optimized/1X/d6407243bedd7a8b0323cffb345cb60750c7f8b8_2_32x32.png'. This request has been blocked; the content must be served over HTTPS.***
2 Likes
How did you install Discourse? This happens when you didn’t setup HTTPS properly.
2 Likes
I had a linux specialist helped me installing. He might have missed something though. If you could steer me to the right direction I am sure he will make things right asap.
1 Like
Looks like the specialist failed to follow the standard install guide.
You need to set force_https to true. It can be done by adding an ENV var for DISCOURSE_FORCE_HTTPS: true in your app.yml and rebuilding.
3 Likes
OK, great. Will relay your advice to the specialist and see if we can fix it.
You guys are awesome. Much appreciated!
1 Like