Images prior 2022 lost

Support

AI-generated summary

Images prior 2022 lost

The discussion revolves around an issue with images uploaded prior to 2022 not being displayed on a Discourse forum running version 3.1.0.beta2. fdanard launched tools to recover the images but was unsuccessful. The issue seems to be related to a change in the FQDN (Fully Qualified Domain Name).

fdanard suspects the change in FQDN is the cause and wonders if there’s a way to update the images with the correct FQDN. Stephen suggests that the domain name change likely caused the issue and recommends remapping/rebaking.

fdanard reveals that the FQDN change occurred over a year ago. fdanard considers using the discourse remap command to update the domain name, as suggested in a Meta Discourse thread. Stephen agrees that this step is required, along with another step, when changing domains.

fdanard discovers that the outdated FQDN is set in the app.yml file under DISCOURSE_CORS_ORIGIN and wonders if updating this and rebuilding would resolve the issue.

1

Hi

We are using the the latest Discourse version r 3.1.0.beta2, and it looks like the images prior 2022 are not displayed.

I launched some tools trying to recover them. No way.

cd /var/discourse/
./launcher enter app
rake posts:missing_uploads
Looking for missing uploads on: default
Fixing missing uploads:
:prohibited::ok_button::ok_button::ok_button::ok_button::ok_button::ok_button::ok_button::ok_button::ok_button::prohibited::prohibited::prohibited::prohibited::prohibited::prohibited::prohibited::prohibited::prohibited::prohibited::prohibited::prohibited::prohibited:

109 post uploads are missing.

101 uploads are missing.
14 of 101 are old scheme uploads.
73 of 392439 posts are affected.

rake uploads:missing
rake uploads:recover_from_tombstone

We’ve got this:

image
image707×264 2.97 KB

However, it looks we can edit the post and the image appears in the edit area.
The difference between image in edit and the image in the forum is.
Side Edit:
<img src="/uploads/default/original/3X/e/8/e8447f3cb3fbeadfbc1757ef6dd3da6a669f15ca.png" ....

Side Forum:
<img src="https://xxxxxxxxxxxxxxxxxx/uploads/default/optimized/3X/e/8/e8447f3cb3fbeadfbc1757ef6dd3da6a669f15ca_2_690x219.png" ...

Is there a way to fix that?

Thanks
Franck

2

It seems the FQDN is changed between the newest images and the oldest images.
The FQDN is not the same.

Is there a way to update the images with the good FQDN?

3

When did your FQDN change?

Sounds like you changed domain name and didn’t remap/rebake.

4

Hmmm good question,
At least more than one years ago probably.

5

Shoudl we use

discourse remap talk.foo.com talk.bar.com

As into this thread : Change the domain name or rename your Discourse

6

That and the step below are both required when changing between domains.

7

Hmm I found something in app.yml with this FQDN:
It is set here: DISCOURSE_CORS_ORIGIN:
Should we change only that and rebuilt?

The FQDN is set here, and it’s no longer available.