ERROR: Could not Retrieve Remote Content

PushButton Content, Images, Videos, Blogs, News - Could not retrieve remote content.

When you get this error have a look at the PushButton log file to find the cause. You can find this file in your main WordPress installation folder under /wp-content/plugins/pushbuttonseo/temp/ and the file is called "log"

Usually these errors arise because the target server has denied the request for information. When Google or YouTube detect a lot of traffic coming from your server's IP address or they detect traffic that is obviously generated by a scraper or robot, they temporarily block the request. Google's initial block takes the form of a CAPTCHA challenge, which unless provided means the request won't be served. The YouTube API simply issues a warning it has received too many requests in too short a space of time.

It is highly unlikely that Pushbutton by itself will cause these blocks. PushButton is an on demand service, you have to be there to press a button in order to make a request. Scrapers and automated tools often run around the clock and can make many requests in short periods of time and often at predictable intervals. This creates a footprint that implies a robot rather than a human has triggered the requests. And that can trigger a block. Switching off the requests for anything between a few minutes and 24 hours usually clears the block unless the problem is triggered repeatedly in which case a block can become permanent.

PushButton uses caches to ensure you are not repeatedly triggering requests for the same information when you update a page. But if other processes are running that are hammering a third party server, PushButton can get blocked too. Guilt by association (or IP address in this case).

On a shared server it may not even be you that is generating the requests. It could be another user scraping Google or running an inefficient lookup service on YouTube. That's just one of the downsides of shared hosting. You never really know who you are sharing with or what sort of a neighbour they make.

If you switch off all scraper and automated services, wait for 24 hours and still see a block then it may be another user on the server causing the problem and you might consider asking your host to move you to another server or at least change the IP associated with your domain. You could also request a dedicated IP which generally costs around $2 a month.

You can technically trigger these blocks with PushButton too. If you rapidly fire different keywords and run many searches in a very short period of time it could result in a temporary restriction of service. But you'd have to be almost deliberately trying to get blocked. Because PushButton requires you type the keywords and manually press the buttons. How many times per minute can you practically do this? Not that many, at least when compared to a robot.

PushButton accesses all content via official (except in one instance) APIs or REST services, there's no scraping going on anywhere. The one case where this is not true is part of the keywords lookup in the premium plugin which access an unofficial but widely used Google service, again using REST and avoiding scraping.

So there's nothing going on the various target services should object to, although terms and conditions can always change. But there are so many other plugins out there that scrape or bypass or hammer, use of any one of them could kill PushButton by getting the server's IP blocked. So please ask yourself the question before assuming a fault with PushButton - "What else am I doing that might result in my server being blocked or blacklisted?"


Article is closed for comments.
Powered by Zendesk