After migrating Discourse to a new server, Bryanpwo reports that images in newly created posts are no longer downloadable or viewable via Lightbox, though older images (pre-migration) still work. The setting download_remote_images_to_local is active, and disk space is not an issue. Attempts to rebake posts and flush Sidekiq queues failed to resolve the issue Bryanpwo. Canapin initially suspected unbaked posts but later acknowledged the issue may stem from configuration or theme/plugin conflicts, referencing a Meta thread where similar issues were reported. Leonardo confirmed the problem affects only post-migration uploads and suggested checking site settings. Bryanpwo shared values for max image width (690) and max image height (500), noting no other image-related settings were modified. The forum is public at forum.endeavouros.com, and a test post (/t/what-games-are-you-playing/6838/948) demonstrates the issue. Rebuilding HTML for affected posts had no effect Bryanpwo. Canapin suggested using the Data Explorer plugin to inspect raw/cooked post fields for debugging. The issue remains unresolved, likely tied to post-migration configuration rather than data or baking.
I successfully migrated Discourse to another server and the only issue is that the uploaded images in posts that were in the backup image are downloadable and viewable as a larger one.
Images that were uploaded in posts after the migration are smaller and not downloadable. download_remote_images_to_local is active.
What am I overlooking?
My guess is that the forum has to rebake all posts for the images to be correctly displayed.
You can have a look at sidekiq to see if there are related tasks running ; if not, try to rebuild a post HTML and see if it “repairs” the post images?
He stated that “download_remote_images_to_local is active.” so I guess this is not the issue. But maybe he ran out a bit of disk space during an automatic rebake of all posts or something like this?
It’s not the disk space, there’s plenty of it. (The VM it is running in still has around 300GB free) I am running baking uncooked posts to see if it solves the issue. I think it is done by tomorrow. It has to rebake 42512 posts.
But the issue is with new posts from after the migration.
Agreed; you said migrated posts are fine so I wouldn’t worry about rebaking or the like. This seems to be an issue with the post-migration configuration.
Are you using an external asset host like S3 or some other object storage API?
Is the site public by any chance, so that we might look at how the posts are rendered?
Failing that, could you paste the raw and cooked fields (inside triple backtick quotes) for a new post that exhibits the issue?
I just rebuild that post with HTML, it didn’t change a thing. I forgot to tell you, but I did try that option in other posts the past few days.
All images until May this year are Lightboxed, after that none of them are, including newly created posts. Before the migration (last week) every image was in Lightbox.