URLs mapped to root domain instead of cdn and wrong url path

סיכום מבוסס בינה מלאכותית

The discussion revolves around URLs being mapped to the root domain instead of the CDN and having incorrect URL paths. Wolftallemo encountered this issue after adding a CDN and rebaking posts, resulting in URLs pointing to domain.com/cdn.domain.com/original/2X/image.png instead of the CDN. They tried to fix it by remapping the URLs but ended up with domain.com/uploads/uploads/default.

Wolftallemo wants to point the URLs back to /uploads/default or, if possible, the CDN. RGJ suggests a solution using script/discourse remap and provides a command that should fix the issue for pointing to /uploads/default.

Wolftallemo asks if this solution can be used for pointing to the CDN, but eventually finds their own solution:

  • Uploading missing files to the S3 bucket using s3cmd
  • Remapping those to the CDN
  • Remapping other incorrect mappings to the CDN
  • Redoing the process for every different type of incorrect mapping

When I added a cdn to the instance I operate, after rebaking all of the posts instead of pointing to the cdn, it pointed to domain.com/cdn.domain.com/original/2X/image.png

After trying to fix it the urls by remapping they pointed to domain.com/uploads/uploads/default

So what I am trying to do is at the very least point it back to /uploads/default or possibly to the cdn again if it won’t be pain and suffering all the way.

This sounds related / familiar to this issue Multisite + short-url + secure_uploads + s3

script/discourse remap //domain.com/uploads/uploads/ //domain.com/uploads/ should do the trick.

Would this work with pointing to the cdn as well or should I look for another method

So after some pain and suffering I found my solution.

  • Upload missing files to s3 bucket with s3cmd
  • Remap those to the cdn
  • Remap more stuff to the cdn (which somehow were mapped to https://uploads)
    And then redo this process for every different type of incorrect mapping