# Strange ONEBOX issue

**URL:** https://meta.discourse.org/t/strange-onebox-issue/234338
**Category:** Bug
**Created:** [July 28, 2022, 11:59pm UTC](https://meta.discourse.org/t/strange-onebox-issue/234338 "2022-07-28T23:59:42Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![BCHK](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bchk/32/3268_2.png) [@BCHK](https://meta.discourse.org/u/BCHK)
#### Post date: [July 28, 2022, 11:59pm UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/1 "2022-07-28T23:59:42Z")

</div>

When I post this link in my forums after it first renders appropriately.

 ![Screen Shot 2022-07-28 at 5.00.16 PM](https://global.discourse-cdn.com/meta/original/4X/8/d/0/8d049c6115dc58a8e7b7df8d4d39f9082a9dec76.png)

actual link below here: [https://neo.life/2022/07/the-buck-institute-where-the-promise-of-aging-research-isnt-longevity/](https://neo.life/2022/07/the-buck-institute-where-the-promise-of-aging-research-isnt-longevity/)

but then a few seconds later I get get a broken link symbol, so, it looks like this in my forum:

 ![Screen Shot 2022-07-28 at 4.59.19 PM](https://global.discourse-cdn.com/meta/original/4X/3/c/1/3c1ac1505f9bd3a4d493846524c410da040d05f6.png)

---

<div class="post-metadata">

### Author: ![darkpixlz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darkpixlz/32/549896_2.png) [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [July 29, 2022, 12:22am UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/2 "2022-07-29T00:22:47Z")

</div>

Weird, does this work on [try.discourse.org](http://try.discourse.org)?

 ![image](https://global.discourse-cdn.com/meta/original/4X/2/0/4/204573e06568ddace17116775db8f49d71e95bba.png)

Edit: I believe this is an issue with your site.

---

<div class="post-metadata">

### Author: ![BCHK](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bchk/32/3268_2.png) [@BCHK](https://meta.discourse.org/u/BCHK)
#### Post date: [July 29, 2022, 12:35am UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/3 "2022-07-29T00:35:51Z")

</div>

No - it also happens here:

This link is here: [https://neo.life/2022/07/the-buck-institute-where-the-promise-of-aging-research-isnt-longevity/](https://neo.life/2022/07/the-buck-institute-where-the-promise-of-aging-research-isnt-longevity/)

but then if I put it on its own line:

[https://neo.life/2022/07/the-buck-institute-where-the-promise-of-aging-research-isnt-longevity/](https://neo.life/2022/07/the-buck-institute-where-the-promise-of-aging-research-isnt-longevity/)

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [July 29, 2022, 12:39am UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/4 "2022-07-29T00:39:57Z")

</div>

Something is certainly off here, we will have a look. Maybe the host is rejecting the user agent for our backend crawler.

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [July 29, 2022, 8:51am UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/6 "2022-07-29T08:51:11Z")

</div>

When accessing the image ([https://neo.life/wp-content/uploads/2022/07/buck-institute-longevity-aging-genetics@2x-1000x714.jpg](https://neo.life/wp-content/uploads/2022/07/buck-institute-longevity-aging-genetics@2x-1000x714.jpg)) programatically (e.g. via curl), we get served a Cloudflare error page with a captcha. So it looks like this site is deliberately blocking robots from downloading the images.

If you trust the site and are happy for images to be permanently hotlinked, then you could add ` neo.life` to the `disabled image download domains` to stop Discourse attempting to download them.

---

<div class="post-metadata">

### Author: ![BCHK](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bchk/32/3268_2.png) [@BCHK](https://meta.discourse.org/u/BCHK)
#### Post date: [July 29, 2022, 6:05pm UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/7 "2022-07-29T18:05:59Z")

</div>

Interesting… I tried to do what you suggested (adding neo.life to the disabled image download domains), then opened the post and re-saved it , but the problem is still evident.

Do I need the http:// in front of the domain for it to work properly?

---

<div class="post-metadata">

### Author: ![BCHK](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bchk/32/3268_2.png) [@BCHK](https://meta.discourse.org/u/BCHK)
#### Post date: [August 4, 2022, 1:26am UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/8 "2022-08-04T01:26:08Z")

</div>

I’m seeing this onebox issue on more and more links lately - another example:

Same thing happens - it renders, then it doesn’t.

[https://www.nature.com/articles/s41586-022-05022-3](https://www.nature.com/articles/s41586-022-05022-3)

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [August 4, 2022, 11:47am UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/9 "2022-08-04T11:47:14Z")

</div>

> [@BCHK](#):
>
> Interesting… I tried to do what you suggested (adding neo.life to the disabled image download domains), then opened the post and re-saved it , but the problem is still evident.

To fix an existing post after changing the site setting, you’ll have to click the 🔧, then “Rebuild HTML”. I just did that on your post above and it’s looking ok here. Can you try that on your site?

> [@BCHK](#):
>
> another example

This one looks like it has a slightly different cause. I’ve tracked it down [a problem in one of Discourse’s dependencies](https://github.com/sporkmonger/addressable/issues/472). We’re tracking this, and will try to get a fix or workaround in place. Thanks for the report!

---

<div class="post-metadata">

### Author: ![BCHK](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bchk/32/3268_2.png) [@BCHK](https://meta.discourse.org/u/BCHK)
#### Post date: [August 5, 2022, 1:40am UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/10 "2022-08-05T01:40:37Z")

</div>

Another example - yes, the rebuild HTML worked in that last case:

But here is another example where I’m getting the broken link image for a respectable sourced link:

> **[Saudi Arabia plans to spend $1 billion a year discovering treatments to slow...](https://www.technologyreview.com/2022/06/07/1053132/saudi-arabia-slow-aging-metformin/)**
>
> The oil kingdom fears that its population is aging at an accelerated rate and hopes to test drugs to reverse the problem. First up might be the diabetes drug metformin.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [August 5, 2022, 2:11am UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/11 "2022-08-05T02:11:21Z")

</div>

Even if the site is considered respectable it doesn’t mean that they’re going to allow images to be crawled and downloaded by bots.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 9, 2022, 10:58pm UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/12 "2022-08-09T22:58:11Z")

</div>

Keep the examples coming @BCHK !

We recently fixed some issues oneboxing guardian, eg:

> **[Hello Kitty: when is a cat not a cat?](https://www.theguardian.com/lifeandstyle/shortcuts/2014/aug/28/hello-kitty-cat-40-anniversary-japanese-london)**
>
> Hello Kitty’s 40th anniversary has turned up some unusual news – she’s not a cute Japanese cat, she’s a young Londoner from the suburbs

The one from MIT is happening cause they send through a favicon to a missing image. We plan to fix this by simply never rendering these broken chains in oneboxes.

---

<div class="post-metadata">

### Author: ![darkpixlz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darkpixlz/32/549896_2.png) [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [August 10, 2022, 7:52pm UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/13 "2022-08-10T19:52:50Z")

</div>

Just noticed a PR was opened that seems to be related to this

[https://github.com/discourse/discourse/pull/17868](https://github.com/discourse/discourse/pull/17868)

---

<div class="post-metadata">

### Author: ![nbianca](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nbianca/32/157984_2.png) [@nbianca](https://meta.discourse.org/u/nbianca)
#### Post date: [August 11, 2022, 6:35pm UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/14 "2022-08-11T18:35:12Z")

</div>

You are correct. That PR is merged and you can see the dead favicon above is no longer showing up as a broken chain icon.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 14, 2022, 11:40pm UTC](https://meta.discourse.org/t/strange-onebox-issue/234338/15 "2022-08-14T23:40:28Z")

</div>


