# Onebox no longer works for my wordpress site
**URL:** https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202
**Category:** Support
**Created:** [6월 8, 2017, 11:40오후 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202 "2017-06-08T23:40:19Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [6월 8, 2017, 11:40오후 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/1 "2017-06-08T23:40:19Z")
Continuing the discussion from [Did onebox change? They're not showing for my main site any longer](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/8):
Not sure what’s going on here or if it’s related to this topic, but my site used to onebox beautifully in discourse - it no longer does as of a week or so, even here on meta. I just updated my discourse to tests passed.. no dice. No changes recently on the wordpress site until we updated some plugins today.
Example URL that should onebox:
```
https://namati.org/resources/childhood-statelessness-in-south-africa/
```
> **[Childhood Statelessness in South Africa](https://grassrootsjusticenetwork.org/resources/childhood-statelessness-in-south-africa/)**
>
> Childhood statelessness in South Africa is a generally unaddressed, largely preventable, but a growing phenomenon. This short publication presents the experiences of 9 children who have been let down…
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [6월 9, 2017, 12:10오전 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/2 "2017-06-09T00:10:06Z")
Are you on latest?
There were these two issues prior
> [@Onebox /almost/ works normally again](https://meta.discourse.org/t/onebox-almost-works-normally-again/64057):
>
> Continuing the discussion from [Did onebox change? They're not showing for my main site any longer](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/8): @eviltrout was totally awesome and made it work again - but it’s still not entirely back to normal. It no longer follows a 302 redirect: [http://tjek.nu/r/aMp0](http://tjek.nu/r/aMp0) should yield the same as: [http://e-liquid-recipes.com/recipe/1351050/Auntie%20J's%20Cream%20Donut](http://e-liquid-recipes.com/recipe/1351050/Auntie%20J%27s%20Cream%20Donut) The first one, results in a HEAD =\> 501 then GET =\> 302 redirect, which should finally lead to a GET =\> 200 You guys rock slight_smile
> [@Did onebox change? They're not showing for my main site any longer](https://meta.discourse.org/t/did-onebox-change-theyre-not-showing-for-my-main-site-any-longer/63901/8):
>
> It’s fixed now: [http://e-liquid-recipes.com/recipe/1121597/Banana%20Cream%20Pie%20(Gmix)](http://e-liquid-recipes.com/recipe/1121597/Banana%20Cream%20Pie%20%28Gmix%29) Was quite involved. The fix wasn’t as simple as to try HTTP GET, but it also involved supporting cookies on redirects which our more secure redirector did not do. Both are supported now.
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [6월 9, 2017, 3:44오전 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/3 "2017-06-09T03:44:53Z")
Thanks @cpradio! Yes, I am on latest.. I updated after reading these posts shortly before starting this topic. Also, it doesn’t work on meta either as you can see above.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [6월 9, 2017, 7:43오전 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/4 "2017-06-09T07:43:18Z")
The OpenGraph data looks OK to me, any ideas @eviltrout?
[Iframely URL Debugger - Open Graph, Twitter Cards, oEmbed](http://iframely.com/debug?uri=https%3A%2F%2Fnamati.org%2Fresources%2Fchildhood-statelessness-in-south-africa%2F)
---
### Author:  [@daath](https://meta.discourse.org/u/daath)
#### Post date: [6월 9, 2017, 8:46오전 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/5 "2017-06-09T08:46:14Z")
Could be because of HTTPS? Though an analysis of the certificate shows that everything should be fine…
---
### Author:  [@daath](https://meta.discourse.org/u/daath)
#### Post date: [6월 9, 2017, 8:47오전 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/6 "2017-06-09T08:47:25Z")
Did you look at the logs in your dashboard? If onebox fails it should write something in the log…
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [6월 9, 2017, 9:08오전 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/7 "2017-06-09T09:08:33Z")
I just pulled onebox and manually added `namati.org` to [https://github.com/discourse/onebox/blob/master/lib/onebox/engine/whitelisted\_generic\_onebox.rb#L18](https://github.com/discourse/onebox/blob/master/lib/onebox/engine/whitelisted_generic_onebox.rb#L18)
So if something is broken it’s probably not directly related to the domain.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [6월 9, 2017, 9:19오전 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/8 "2017-06-09T09:19:56Z")
Given [https://github.com/discourse/discourse/blob/master/lib/onebox/engine/whitelisted\_generic\_onebox.rb#L9](https://github.com/discourse/discourse/blob/master/lib/onebox/engine/whitelisted_generic_onebox.rb#L9)
It will return `true` for `namati.org` so the domain should be automatically whiteslisted as far as I understand onebox at the moment.
---
### Author:  [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [6월 9, 2017, 3:27오후 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/9 "2017-06-09T15:27:12Z")
That site seems to be returning nothing for our custom user agent `Discourse Forum Onebox vXXX`
If I use `Ruby` like the onebox does outside of Discourse the onebox works fine.
So this must be the result of our new user agent string.
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [6월 9, 2017, 8:01오후 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/10 "2017-06-09T20:01:02Z")
> [@eviltrout](#):
>
> So this must be the result of our new user agent string.
So maybe I need to check with my wordpress host, wpegine, about accepting this user agent string?
---
### Author:  [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [6월 12, 2017, 3:09오후 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/11 "2017-06-12T15:09:41Z")
Yes that would be a good thing to do. It’s curious they accept `Ruby` but not ours.
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [6월 12, 2017, 4:16오후 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/12 "2017-06-12T16:16:52Z")
OK, looks like my problem is solved. From wpengine chat:
> Yep it does look like it came and got a 200 OK! I added a rule to your server config file to outright allow the user agent.
I can confirm that it’s now working again - also in the OP above which I just edited as a test. 🚀
---
### Author:  [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [6월 12, 2017, 4:37오후 UTC](https://meta.discourse.org/t/onebox-no-longer-works-for-my-wordpress-site/64202/13 "2017-06-12T16:37:10Z")