Facebook Images Slowly Stopped Working

When experiencing issues with Facebook previews, a good first step is to enter some of your posts’ URL into Facebook’s debugger. You’ll find out what Facebook sees when visiting your site to gather information to build post previews.

I did so and checked one of your latest posts:
https://auburnmassdaily.com/2014/02/13/girls-hockey-flattens-matignon/
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fauburnmassdaily.com%2F2014%2F02%2F13%2Fgirls-hockey-flattens-matignon%2F

I kept getting 2 types of errors, as follows:

https://i.wpne.ws/TuE3
https://i.wpne.ws/TuGp

In the first one, Facebook doesn’t even seem to be able to access your site at all, which is why I tried again, I thought it could be a glitch with the debugger.
In the second, Facebook’s crawler seems to be redirected to a different URL that doesn’t exist.

Do you use a plugin or a service that may create such redirections, or block Facebook’s crawler from browsing your pages? If so, could you try to deactivate it and see if it helps?

Once Facebook’s debugger stops returning errors, Publicize should start working again.

Let me know how it goes.

Interesting, thanks. I did try the debugger, but I got an error, too, saying the URL wasn’t there or something like that. I don’t think I have anything redirecting, but thanks for pointing me in the right direction. I’ll do more digging.

Now I was able to get debugger to work on a post, I did not receive any errors. Everything looked fine, in fact. Pulled the correct image. Had the correct description, etc. Fetched the proper URL….

I did deactivate all other plugins. I also deactivated, and reactivated, JetPack, and I still cannot connect to Facebook using Publicize. When I use the Facebook link I get error Error code: -32301. If I use the Connect button to the right of the Facebook logo I get error code: Error code -32300.

The same thing happened when I tried to connect with Path and LinkedIn, but Tumblr works…?

When I manually use the Sharing button on each post, I can post to Facebook, but only the url, no picture or title are being posted, although when I ran the FB debugger it showed no problems with those.

What is incredibly frustrating is this is an exact repeat of what I went though last fall. Publicize all worked like clockwork, then I noticed a couple errors, then there was a complete JetPack failure. I was given all these workarounds, and codes to screw with and whatnot and none of it worked. It suddenly started working correctly again one day. Update or something? I don’t recall.

What I can tell you is this worked fine as of Feb. 6, and as I shared in the link above, started with errors, now it completely does not work. There have been no updates or changes to our site admin in that time. Nothing.

The debugger still returns the same 2 errors for me:
https://i.wpne.ws/TvDY
https://i.wpne.ws/TuRq
As I refresh the debugger page, it switches from one error message to the other.

After 5 or 6 refreshes, I got a success message:
https://i.wpne.ws/TvIL

But upon refresh, the error message came back, this time different since no redirect URL was mentioned:
https://i.wpne.ws/Tv7h

I then checked the status of your Jetpack connection: in my connection tests, my requests to your site’s XML-RPC file (that’s the file used by your site to communicate with external services like WordPress.com) often returned a 408 (time out) error. That’s probably why you’re seeing this 32301 error.
Like with Facebook’s debugger, this was not always the case though; I repeated my tests multiple times and sometimes it seemed to connect properly. In other tests, I couldn’t access XML-RPC because your domain name servers could not be found.

All these tests seem to point towards some problems with your site. Since you did not make any changes or updates to your site in the past few weeks, that leaves us with 2 options:

• Your hosting provider (BlueHost) made some changes to your server configuration.
• Your site was hacked, and a malicious script is creating these redirections.

I checked your site with Sucuri’s site scanner and it didn’t find any malware:
https://sitecheck2.sucuri.net/results/auburnmassdaily.com/

It doesn’t mean that your site is safe, though. It might be good to go through the steps described here to make sure your site is secure:
https://codex.www.ads-software.com/FAQ_My_site_was_hacked

You could also contact your hosting provider and ask them to have a look at your site settings; they might be able to help.

Let me know how it goes.

Thanks. I will contact Bluehost. I know they did a kernal update over the past couple days (I say that like I know what I’m talking about, but that’s just what the e-mail said!). Appreciate your digging into this.

As an aside, I tried to do what I think you described above, and never did get any kind of error message. I have also not had any problems with public site access.

I have also not had any problems with public site access.

I can also access your site properly, so that’s reassuring I think ??

I tried to do what I think you described above, and never did get any kind of error message

I only did 2 things, that you could try on our end or suggest to BlueHost (or you could send them a link to this thread ?? ):

1. I kept hitting the “Debug” button on this page to see what Facebook sees when visiting one of your posts. I clicked on “Debug” several times because the results were not always the same, as I mentioned above.
2. I checked the status of your Jetpack connection here. I also refreshed the page multiple times there, since the results were not always the same. This debug tool does several things, but to check whether your site accepts incoming connections it does the following call:

   curl -is -H 'Content-Type: text/xml' --data '<?xml version="1.0"?><methodCall><methodName>demo.sayHello</methodName><params></params></methodCall>' 'https://auburnmassdaily.com/xmlrpc.php' && echo

Hopefully that can help BlueHost!

Ok, I am seeing what you mean about the redirect. I talked to my host, they helped me to check for any hacking or malicious activity. None apparently. They also went through settings on their end and nothing changed that should have affected this.

I switched to Theme 2014, disabled all plugins except Jetpack, and still received the error message. I then ran the Jetpack compatibility. I also noticed that since yesterday, I AM able to share my posts manually to Facebook and the image, Title, Excerpt, etc all appear properly. Still no luck on the Publicize end though. I also have no luck now connecting to other social media sites. Does this help at all?

Site info

SITE_URL: https://auburnmassdaily.com
HOME_URL: https://auburnmassdaily.com

TEST: HTTP Connection
Array
(
[headers] => Array
(
[server] => nginx
[date] => Sat, 15 Feb 2014 16:31:13 GMT
[content-type] => text/plain;charset=utf-8
[connection] => close
[vary] => Cookie
[x-pingback] => https://jetpack.wordpress.com/xmlrpc.php
[expires] => Wed, 11 Jan 1984 05:00:00 GMT
[cache-control] => no-cache, must-revalidate, max-age=60
[pragma] => no-cache
[x-hacker] => Jetpack Test
)

[body] => OK
[response] => Array
(
[code] => 200
[message] => OK
)

[cookies] => Array
(
)

[filename] =>
)

TEST: HTTPS Connection
Array
(
[headers] => Array
(
[server] => nginx
[date] => Sat, 15 Feb 2014 16:31:14 GMT
[content-type] => text/plain;charset=utf-8
[connection] => close
[vary] => Cookie
[x-pingback] => https://jetpack.wordpress.com/xmlrpc.php
[expires] => Wed, 11 Jan 1984 05:00:00 GMT
[cache-control] => no-cache, must-revalidate, max-age=60
[pragma] => no-cache
[x-hacker] => Jetpack Test
)

[body] => OK
[response] => Array
(
[code] => 200
[message] => OK
)

[cookies] => Array
(
)

[filename] =>
)

TEST: Self Connection
Array
(
[headers] => Array
(
[date] => Sat, 15 Feb 2014 16:31:15 GMT
[server] => Apache
[vary] => Accept-Encoding
[connection] => close
[content-type] => text/plain
)

[body] => XML-RPC server accepts POST requests only.
[response] => Array
(
[code] => 200
[message] => OK
)

[cookies] => Array
(
)

[filename] =>
)

UPDATE: So, for giggles, I tried some alternatives. First, I used the dlvr.it web-based app. It seems to be working flawlessly. I also tried the NextScripts SNAP plugin. The configuration was a bit more weighty than I am comfortable with, but guess what? Seems to work.

So, I had a setup that worked. It stopped working. You have had me check everything else except Jetpack. I finally disabled Jetpack and ran other tools that do what Publicize is supposed to do, and they worked. Soooooo, we seem to have narrowed the problem to one focused on JetPack, no?

I would simply shut this down and move on to plugins that work, except that I did appreciate the integration of Publicize…when it worked.

At this point, I am tired, so if you have any suggestions about making your plugin work properly, instead of blaming every other link in the chain (Facebook, my theme, other plugins, my host….), I am all ears. Otherwise I guess we’ll be jettisoning JetPack as well.

I don’t mean to blame anyone, I was just pointing out what’s causing Jetpack to fail: Facebook still reports issues when entering some of post URLs in the debugger.
Here is a screenshot of my latest test, a few seconds ago.

As long as Facebook Debugger returns errors, your Publicize posts will be rejected by Facebook. I can’t speak for any other plugins, though, as I don’t know how they push updates to Facebook.

If other plugins work where Jetpack Publicize doesn’t, if BlueHost or yourself cannot find what’s creating the redirections, and if your site was no hacked, I guess it’s best to deactivate the Publicize module and use another plugin instead. I’m afraid I can’t be of more help, as I don’t know what’s creating this redirection.
I was able to find 2 other threads reporting similar issues, but the users do not seem to have found the source of the problem:
https://www.ads-software.com/support/topic/random-302-redirects-to-my-own-site?replies=2
https://stackoverflow.com/questions/8870344/facebook-debug-tool-giving-bad-response-code-redirect-for-my-site

Let me get this straight, after going through all of the above, and my tracking through every possible problem with my site not working with Publicize from my end – scrutinizing my site, talking to my host, disabling every other plugin, and finally resorting to a different sharing service entirely.

Then Jetpack releases an update today and lo and behold Publicize works fine on my site again. But the problem was from my end all along. Right.

I really want to like and use Jetpack. I really do. But you all make it really, really hard.

Regardless of the version of Jetpack you use, Facebook Debugger is still the go-to resource when looking at Publicize issues.

I don’t see any error when entering a post URL in Facebook Debugger at the moment:

• https://i.wpne.ws/U8rL

As long as the debugger returns results without warnings, Publicize should work.

Now I don’t know how you solved the redirection issues that happened in the past, but whatever you did, it worked ??

Critical Errors That Must Be Fixed

Could Not Follow Redirect URL requested a HTTP redirect, but it could not be followed.

Warning

Errors that must be fixed
Missing Required Property The og:type property is required, but not present.

im getting this errors in Facebook Debugger

thanks

@yoluca Could you please start your own thread, as per the Forum Welcome?
https://www.ads-software.com/support/plugin/jetpack#postform

You’ll also want to let us know your site URL so we can take a look at the problem. If you want it to remain private, you can also contact us via this contact form:
https://jetpack.me/contact-support/

Thank you!

ok

thanks

Thats happens to me too
today i was working on a web site for Holi colorfull festival of india
and when i publish a post,Publicize plugin update my fb wall with its titile, description and my gravtar pic but it should show featured pic of post.
I resolve this problem by disable plugins that automatically generates OG: tag in wordpress.