Here’s how to reproduce this bug: ./launcher bootstrap app with a.com as hostname in app.yml Upload a picture in a post. Let’s say it is http://a.com/uploads/default/original/xxxx.png ./launcher rebuild app with b.com as hostname in app.yml Open the post in Step 2, you will see a broken picture. Y…

Got it to work now and pictures are back on the forum, here was how: -udiscourse RAILS_ENV=production bundle exec ./script/discourse remap <old> <new> Thanks for all the help! :heart_eyes:

When you rebuild the post (rebuild html), is the problem fixed ? If it’s fixed, you’ll have to rebale all posts cd /var/discourse ./launcher enter app rake posts:rebake

Only rake posts:rebake won’t work. But just one minute ago I found a “solution”: discourse remap a.com b.com rake posts:rebake Then I got this: ... Remapping uploads origin 1 rows affected! Remapping oauth2_user_infos uid 0 rows affected! Remapping oauth2_user_infos provider 0 rows affected! Rem…

Thank you for your response. If the old hostname is not unique enough, then remap will generate unwanted results. Besides, the URLs in editor are already stored as relative path. That’s why pics are working in preview mode. For external pictures, they are “optimized”. For internal pictures, I wo…

[이미지] andy1247008998: If the old hostname is not unique enough, then remap will generate unwanted results. So don’t remap example.com example.net, but instead remap //example.com/ //example.net/.

Hello! I’m having a similar problem with posted images on the forum I’m working on, I also have a support thread about it. The background is a little different: I haven’t renamed the forum, but I did migrate it to docker and set up HTTPS. We use AWS and the S3 bucket’s name had forbidden character…

[이미지] victoria: Is it possible to use remap to point these images to the new bucket name? Yes. If the old bucket name is unique enough, you can just remap on that, otherwise you’ll want to expand out the string (to include, say, the full domain) to avoid false matches. The remap process is …

[이미지] mpalmer: If the old bucket name is unique enough, you can just remap on that Well I don’t think that is so easy to know :confused: If the old bucket name is something like this some.bucket.name.s3.amazonaws.com, the new one is simply some-bucket-name.s3.amazonaws.com If I understood…

[이미지] victoria: If I understood correctly you mean that I could run the whole thing like so: discourse remap some.bucket.name.s3.amazonaws.com some-bucket-name.s3.amazonaws.com And that might be better? Yes, that’s the best way to do it, to avoid the possibility of someone having typed some…

Okay, so I ran that command, but I got this error: /usr/local/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- thor (LoadError) from /usr/local/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' from ./script/discourse:3:in `<main>' I’ll …

Broken image URL paths after changing hostname

Support

zogstrip 7월 24, 2016, 9:17오후 4

The URLs of the uploads are “optimized” (i.e. made absolute and use CDN when enabled) when cooking a post for performance reasons. The solution to your problem is indeed a remap. More can be found here

글		댓글	조회수
After backup restore on other server, uploaded images are broken Support	6	1673	10월 28, 2021
Rebaking old posts won't pull new S3 CDN URL after S3 bucket rename Self-hosting	13	2035	1월 12, 2021
Hosted to self-hosted migration: past uploads still reference discourse infra Support	15	830	10월 16, 2023
Image uploads path in posts will not change after rebake and remap Support	3	1329	4월 6, 2020
Updating image URL's after a domain change Support	5	1037	2월 3, 2021

Broken image URL paths after changing hostname

Related topics