Did a restore and all the internal links have the test URL domain, breaking all the links and I am not sure why it did not take up the correct site URL, without going into the code/db to do a mass find & replace any solutions on how to do this another way? I was thinking do a Re-Restore?

The remap rethink worked as suggested by @pfaffman but was actually the catalyst for the solution, not not the solution per se, it helped me figured out what I was doing wrong, it remapped me eyes! If I had read the error properly i.e. paid attention. I would have solved this a long time ago as I w…

You’ll need to go into the db and do a mass search/replace. There is a tool for that: RAILS_ENV=production discourse remap //old.domain //new.domain

Thanks. That looked easy enough. I entered the app and I ran that but it seems not to have changed the instances of the URLs in the posts. This was the remap: RAILS_ENV=production discourse remap //https://sub.domain.com //https://domain.com This ran and competed on the “default” DB it took a f…

[image] agemo: RAILS_ENV=production discourse remap // https://sub.domain.com // https://domain.com That should be RAILS_ENV=production discourse remap //sub.domain.com //domain.com The reason for // is that it matches http://, https:// and protocol-less URLs, and it does not match e-mail add…

Yea ok, then same error again: Remapping tables on default... Error: ERROR: duplicate key value violates unique constraint "index_post_hotlinked_media_on_post_id_and_url_md5" DETAIL: Key (post_id, md5(url::text))=(1001176, 547048fcd29cdac60) already exists. The remap has only been partially appl…

No further ideas? Apart from this rails remap impasse I thought maybe if I backup the db and do a restore again it might remap the Link-urls correctly during the restore process?

The error I am still hitting seems to be the repeat or very similar to the stop error here that needed a fix: [image] Upgrade fails on duplicate key error ("index post hotlinked media on post id and url md5") Bug Had an automatic rebuild fail, looks like …

Does this look more like a bug?

That table has links with both of those domains, so when you try to remap them you get a duplicate key. It’s not a bug. You’re trying to create a duplicate key. You could remove the items from that table that have the apex domain. A better idea is to use www instead of the apex domain.

Thanks. My only concern is this discourse deployment suffers the non-www / SSL issue too, for e.g. How to add ssl to non-www domain? but I will try the remap you suggest and if it works it will force me to solve the non-www issue too! :slight_smile:

Restored Site - URLS need to be corrected, any ideas?

Product Support

pfaffman (Jay Pfaffman) February 6, 2025, 7:00pm 3

You can fix it as described, but that shouldn’t happen.

Did you make and restore the backup using /admin/backups?

Do both systems have the hostname set correctly?

Topic		Replies	Views
Error running remap after changing site url Self-hosting sql-query , domains , postgres	12	472	July 3, 2026
Error on attempting to remap links Bug	6	932	November 18, 2023
`discourse remap` failed Self-hosting	4	840	March 19, 2020
Links broken after move Self-hosting	10	1779	December 15, 2019
Remap failure when changing discourse domain Self-hosting	1	325	May 2, 2024

Restored Site - URLS need to be corrected, any ideas?

Related topics