# Cosa causa rake uploads:fix\_relative\_upload\_links

**URL:** https://meta.discourse.org/t/what-causes-rake-uploads-fix-relative-upload-links/120617
**Category:** Support
**Created:** [17 Giugno 2019, 11:04pm UTC](https://meta.discourse.org/t/what-causes-rake-uploads-fix-relative-upload-links/120617 "2019-06-17T23:04:31Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [17 Giugno 2019, 11:04pm UTC](https://meta.discourse.org/t/what-causes-rake-uploads-fix-relative-upload-links/120617/1 "2019-06-17T23:04:31Z")

</div>

I just did an import from smf2. It worked fine on my machine but when the client ran it, a bunch of images got tombstoned, and recover from tombstone says to run

```
 rake uploads:fix_relative_upload_links

```

Does anyone have a guess what might have gone wrong?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [19 Giugno 2019, 1:14pm UTC](https://meta.discourse.org/t/what-causes-rake-uploads-fix-relative-upload-links/120617/2 "2019-06-19T13:14:49Z")

</div>

And now a bunch of images are just failing to render. That is, something like

```plaintext

![Green.jpg|1200x500](upload://6YplhQc9EFUmImEodEaVrSE7wMl.jpeg) 

```

is rendering `https://host.com/images/transparent.png`

---

<div class="post-metadata">

### Author: ![Brad\_Wood](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/brad_wood/32/204558_2.png) [@Brad\_Wood](https://meta.discourse.org/u/Brad_Wood)
#### Post date: [12 Gennaio 2021, 9:28pm UTC](https://meta.discourse.org/t/what-causes-rake-uploads-fix-relative-upload-links/120617/3 "2021-01-12T21:28:23Z")

</div>

Ciao @pfaffman, hai trovato una soluzione a questo? Sto vedendo il file transparent.png in questa discussione: [Rebaking old posts won't pull new S3 CDN URL after S3 bucket rename - #10 by Brad\_Wood](https://meta.discourse.org/t/rebaking-old-posts-wont-pull-new-s3-cdn-url-after-s3-bucket-rename/175882/10)

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [12 Gennaio 2021, 9:45pm UTC](https://meta.discourse.org/t/what-causes-rake-uploads-fix-relative-upload-links/120617/4 "2021-01-12T21:45:59Z")

</div>

Sì, ho visto il tuo post precedente e non avevo una buona risposta. Quella roba di S3 può essere complicata. La mia migliore risposta gratuita è assicurarti di seguire l’esempio in [Utilizzo dell’archiviazione oggetti per i caricamenti (S3 e cloni)](https://meta.discourse.org/t/using-object-storage-for-uploads-s3-clones/148916) (con CDN per Discourse e il bucket). Se ciò non funziona e hai un budget, posso dare un’occhiata più da vicino (e la prima cosa che farei è proprio ciò che ho appena consigliato!).
