# Links de imagens apontam para subdomínio incorreto (anterior) após migração

**URL:** https://meta.discourse.org/t/image-links-point-to-incorrect-previous-subdomain-after-migration/77884
**Category:** Support
**Created:** [Janeiro 12, 2018, 8:05pm UTC](https://meta.discourse.org/t/image-links-point-to-incorrect-previous-subdomain-after-migration/77884 "2018-01-12T20:05:34Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [Janeiro 12, 2018, 8:08pm UTC](https://meta.discourse.org/t/image-links-point-to-incorrect-previous-subdomain-after-migration/77884/2 "2018-01-12T20:08:23Z")

</div>

This maybe helpful for You but wait for an advice from @pfaffman first

> [@Images tombstoned after import](https://meta.discourse.org/t/images-tombstoned-after-import/74912):
>
> It seems that after an import images get moved to tombstone. I run rake uploads:recover\_from\_tombstone and they come back, but I would rather figure out how to avoid waiting for them to get tombstoned and then move them back. I’ve seen @gerhard recommend running redis on the dev box, but I just do a backup and move them to production. Is that what my problem is?

---

_[View the full topic](https://meta.discourse.org/t/image-links-point-to-incorrect-previous-subdomain-after-migration/77884)._