# Image upload processing

**URL:** https://meta.discourse.org/t/image-upload-processing/356229
**Category:** Support
**Created:** [March 7, 2025, 9:28am UTC](https://meta.discourse.org/t/image-upload-processing/356229 "2025-03-07T09:28:09Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![noid](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@noid](https://meta.discourse.org/u/noid)
#### Post date: [March 7, 2025, 9:28am UTC](https://meta.discourse.org/t/image-upload-processing/356229/1 "2025-03-07T09:28:09Z")

</div>

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

 ![Screen Shot 2025-03-07 at 11.14.22 AM](https://global.discourse-cdn.com/meta/original/4X/5/f/9/5f96ee43efd971b66ae1dd8b0182ee77d6de54cf.png)

---

<div class="post-metadata">

### Author: ![Arkshine](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/arkshine/32/298682_2.png) [@Arkshine](https://meta.discourse.org/u/Arkshine)
#### Post date: [March 7, 2025, 1:04pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/3 "2025-03-07T13:04:16Z")

</div>

Hello, can you look at the browser’s console and see if you get any errors when it happens?

---

<div class="post-metadata">

### Author: ![noid](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@noid](https://meta.discourse.org/u/noid)
#### Post date: [March 7, 2025, 4:47pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/4 "2025-03-07T16:47:48Z")

</div>

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!

```plaintext
***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.***

```

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [March 7, 2025, 4:55pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/5 "2025-03-07T16:55:56Z")

</div>

How did you install Discourse? This happens when you didn’t setup HTTPS properly.

---

<div class="post-metadata">

### Author: ![noid](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@noid](https://meta.discourse.org/u/noid)
#### Post date: [March 7, 2025, 5:02pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/6 "2025-03-07T17:02:35Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [March 7, 2025, 5:06pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/7 "2025-03-07T17:06:26Z")

</div>

Looks like the specialist failed to follow the [standard install](https://meta.discourse.org/t/142537?silent=true) 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.

---

<div class="post-metadata">

### Author: ![noid](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@noid](https://meta.discourse.org/u/noid)
#### Post date: [March 7, 2025, 5:28pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/8 "2025-03-07T17:28:02Z")

</div>

OK, great. Will relay your advice to the specialist and see if we can fix it.  
You guys are awesome. Much appreciated!

---

<div class="post-metadata">

### Author: ![NFULFX](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nfulfx/32/503284_2.png) [@NFULFX](https://meta.discourse.org/u/NFULFX)
#### Post date: [July 20, 2025, 1:59pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/9 "2025-07-20T13:59:47Z")

</div>

I’m suddenly getting this error but only when uploading from a mobile device, not from a desktop. I tried logging into the console to do the “RAILS C” and “sitesetting.force\_https = true” command but I got a “command not found” error.

I do not see “force https” in the forum’s admin settings.

Can someone provide the steps for the “ENV Var” step above? Thank you for your time.

---

<div class="post-metadata">

### Author: ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [July 20, 2025, 3:50pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/10 "2025-07-20T15:50:48Z")

</div>

> [@Falco](#):
>
> DISCOURSE\_FORCE\_HTTPS: true

Try setting it in your app.yml file instead.

---

<div class="post-metadata">

### Author: ![NFULFX](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nfulfx/32/503284_2.png) [@NFULFX](https://meta.discourse.org/u/NFULFX)
#### Post date: [July 20, 2025, 6:35pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/11 "2025-07-20T18:35:22Z")

</div>

Thank you for the suggestion. I included the entry, saved the file and followed the process of rebuilding from here:

> [@Set Environmental Variables](https://meta.discourse.org/t/set-environmental-variables/270832):
>
> notebook_with_decorative_cover This is a #how-to guide for setting up environmental variables in a self-hosted Discourse installation. person_raising_hand Required user level: Administrator Environmental variables play a crucial role in configuring your Discourse instance. They can store sensitive data like API keys and database passwords, making your installation more secure and flexible. In Discourse, environmental variables are set in the app.yml file within your Docker container setup…

After trying again with a cleared cache on the browser, I am able to pass the “processing upload” from a mobile browser. Thanks!

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 5, 2025, 4:30pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/12 "2025-11-05T16:30:07Z")

</div>

This specialist did a [standard install](https://meta.discourse.org/t/142537?silent=true). Inside the container I get this:

```plaintext
# set|grep FORCE_HTTP
DISCOURSE_FORCE_HTTPS=true

```

And the behavior is that uploads on mobile don’t work ,but on mobile, switching to the Desktop View makes uploads work:

> [@](#):
>
> I’m making the distinction that I’m still on my phone, but using the “view as website as desktop” or force it to NOT use mobile mode. When I change to that mode on my phone, it uploads fine. Which makes me think it’s not a problem with my phone’s performance. Should switching between desktop view and mobile view really do much?
> 
> But after a while, I’m now getting it again. It’s just really inconsistent. Does javascript code change between the mobile/desktop modes in the same browser? See here:  
> [Uploads involving client-side JS preprocessing fail in Chrome based browsers - #8 by LVA](https://meta.discourse.org/t/uploads-involving-client-side-js-preprocessing-fail-in-chrome-based-browsers/348342/8)

@noid --what mobile browser and OS are you using?

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [December 5, 2025, 4:30pm UTC](https://meta.discourse.org/t/image-upload-processing/356229/13 "2025-12-05T16:30:57Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
