Onebox no longer works for my wordpress site

[tobiaseigen]

Continuing the discussion from Did onebox change? They're not showing for my main site any longer:

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

[cpradio]

Are you on latest?

There were these two issues prior

Onebox /almost/ works normally again

Continuing the discussion from Did onebox change? They're not showing for my main site any longer: @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: should yield the same as: The first one, results in a HEAD => 501 then GET => 302 redirect, which should finally lead to a GET => 200 You guys rock

Did onebox change? They're not showing for my main site any longer

It’s fixed now: 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. https://github.com/discourse/discourse/commit/53b95f009fc457f033427147ce34b4aa2e472f74 https://github.com/discourse/discourse/commit/369bb78f8e49c4cc4c3b585b40e4dc143a8b2669 https://github.com/discourse/onebox/commit/ea4a45bbf452bc3c40d470889daf21faa7fa6ba0

[tobiaseigen]

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.

[codinghorror (Jeff Atwood)]

The OpenGraph data looks OK to me, any ideas @eviltrout?

http://iframely.com/debug?uri=https%3A%2F%2Fnamati.org%2Fresources%2Fchildhood-statelessness-in-south-africa%2F

[daath (Lars)]

Could be because of HTTPS? Though an analysis of the certificate shows that everything should be fine…

[daath (Lars)]

Did you look at the logs in your dashboard? If onebox fails it should write something in the log…

[joffreyjaffeux]

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

So if something is broken it’s probably not directly related to the domain.

[joffreyjaffeux]

Given 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.

[eviltrout (Robin Ward)]

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.

[tobiaseigen]

@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?

[eviltrout (Robin Ward)]

Yes that would be a good thing to do. It’s curious they accept Ruby but not ours.

[tobiaseigen]

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.