# Onebox issue with a specific site **URL:** https://meta.discourse.org/t/onebox-issue-with-a-specific-site/104408 **Category:** Support **Tags:** onebox **Created:** [December 16, 2018, 11:31am UTC](https://meta.discourse.org/t/onebox-issue-with-a-specific-site/104408 "2018-12-16T11:31:31Z") **Posts on this page:** 1 **Showing post:** 15
### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield) #### Post date: [January 23, 2019, 1:30pm UTC](https://meta.discourse.org/t/onebox-issue-with-a-specific-site/104408/15 "2019-01-23T13:30:26Z")
Just an update to this, I figured it would be interesting to see if I could find a workaround _without_ moving server. I’ve successfully monkeypatched `Oneboxer` and `Onebox::Helpers` in a local plugin to call a proprietary third party API to bring back the target page source reliably if the direct response is `nil` (ie my request was rejected). There is a (very) small charge to my API account every time I call it so it needs to be used sparingly for those sites that are _tricky_. The advantage is I can remain on a cheap-as-chips server whilst not having to worry about its ‘reputation’ (a bit like using a 3rd party mail service). The code still works as normal for sites that don’t reject my first request so I’m not charged for the majority of previews. I anticipate that the costs of using the third party API will be much lower than the increase in costs for moving to a VPS provider with a more trusted reputation. But in anycase _problem solved_. Thanks to everyone who weighed in. **This is now [a working plugin](https://meta.discourse.org/t/onebox-assistant-a-plugin-to-help-onebox-do-its-job/107405).** --- _[View the full topic](https://meta.discourse.org/t/onebox-issue-with-a-specific-site/104408)._