Publicize stopped working

Same here. The last post that propagated was 8 hours ago. The latest 4 posts on my site have not been distributed.

https://www.allspark.com/content

Same issue here… i just tried posting my article at 12:01 AM like I do every night and my share to FB, GooglePlus, and Twitter all didn’t go through… my emails to my subscribers did… but none of the sharing medias did? My site is:

https://www.thetwelfthstep.com

Update… my sharing went through 32 minutes late… it just showed up on all three at the same time, but 32 minutes past when it actually posted on my site as well as when the e-mails went out?

One last update before I head to bed… i tried a test posting at 12:13 am and as of 1:30am it still hasn’t showed on on FB, GooglePlus, or Twitter… the first one from 12:01 AM as I said before, showed up at 12:33am on all three, but the second one never did… I checked with GoDaddy who hosts my blog and the issue wasn’t on their server… it’s definitely with Jetpack and I’m wondering if the queue is backed up or shut down right now to send out sharing requests?

Have either of you posted today and had the sharing work successfully? I haven’t tried yet and was just wondering?

@coldplay0484 and @kalidor: What are your sites’ URLs?

@andrew: I’m not seeing anything in our error log for your site. Regarding the e-mails being sent out, are you using Jetpack’s Subscriptions module (e.g. were those Jetpack e-mails you’re referring to).

The systems are connected so if the e-mails are going out, then the Publicize system is being fired too. Trying to isolate down all of the variables.

We have had a number of problems with GoDaddy lately (blocking Jetpack’s access to servers as part of an attempt to mitigate a XMLRPC brute force attack), though the debugging information looks clean for your site now.

Thanks!

Mine is https://www.allspark.com/content

It looks like it’s working normally now. I also experienced the same symptoms of stuff showing up 30 to 40 minutes after I posted it last night, but when I got up this morning and saw that my staff had posted several articles it appeared they all went through okay and are continuing to do so.

The reason I narrowed it down to Jetpack (as opposed to say, Facebook in particular) is that it wasn’t hitting Twitter or G+ either and the delayed posts were propagating out to them simultaneously.

As far as hosting, I’m not on Godaddy but rather have a co-located server at my local ISP.

Brandon, i’m not sure if i understand your question. On the sharing menu, I have FB, Twitter, and Googleplus set up and its connected. Everything has been running fine until last night. In regards to my subscribers… the emails that went out are the ones to those who fill in the “subscribe to this blog” widget. I guess they are the jetpack subscribers because when I go look at the Jetpack site stats page it shows down at the bottom the subscribers to my blog. So yes, they went out fine. But at 12:01am, that was fine and so was my blog posting on the web, but the sharing didn’t work initially and then suddenly at 12:33am, 30 minutes or so later, it shows up on all three. I’m not sure how the sharing side works… but I”m a little concerned about what you are saying with GoDaddy. Is this going to be a reoccurring problem? I’m not sure I understand what you mean by a brute force attack? What would cause a 30 minute delay for my one blog to share on the media sites, and then the second never showed up?

There might be a slight backup on our end (but not something big enough to merit an all-hand alert). I’ll run this by our Publicize and Systems folks to confirm it is/was on their radar.

Our Publicize does work as an async job (meaning we’ll let your site continue with the publishing process while our jobs system sends out the link to the social media networks). Generally, the job will complete within 5-15 seconds after publishing, but the system is built that it’ll still continue, even if it takes longer, without causing a problem for your site (e.g. the other way would be your site waiting on us to finish and respond back, which could cause more visible problems for you if our systems were having issues, if the social media networks were having issues, or if the process simply took 45 seconds instead of 5).

In short, I’ll make sure the right parties are on top of things. Cheers!

@andrew

The brute force attack that GoDaddy was mitigating was they were seeing a number of servers being hit by a number of infected computers trying to “guess” a password for a lot of sites. They blocked the communication method being used, which is the same one Jetpack uses.

Overall, it shouldn’t be a problem long term and we’ve been in communication with GoDaddy’s security team to find a good way for them to handle this without impairing your site.

I don’t have more information on the source of the 30min delay, but it does sound so far to be a temporary delay and not a systemic problem.

Well Brandon, if Kalidor had the same issue as me last night with the delay and he’s not on GoDaddy, then it’s not GoDaddy here. But I am curious on one thing. I tried a second post last night that I just put “Testing” and a few other words on the subject line and the same in the body… I did that at 12:13AM and while it did again post on my site and then send out the jetpack emails, it never got to FB, Googleplus or Twitter at all. I ended up deleting the post on my site around 12:30am or so… does doing that remove the async job and that’s why it never showed up?

@andrew

My immediate response is deleting the post could likely cause it not to post. I’m not 100% sure without further investigation since the Publicize system rarely takes along enough for that to come up ??

Agreed, it doesn’t sound like a hosting issue, but did want to note that since we’ve had a high number of issues for GoDaddy-hosted sites in the last few weeks.

Signing off, have a good night y’all.

Fair enough, maybe because of the delay and my deleting it, it was able to delete it from the async job? I just thought it strange that the other one showed up but this one didn’t. I guess I’m just not sure how the jetpack share works. Is there a function on each of our hosting servers that queues up the post or is it that there’s a queue somewhere else it goes to… you mentioned there might have been a backup last night… i’m just wondering how the whole process works. In other words, my blog is hosted on Godaddy, when the scheduled post gets put on the web, where is the programming logic for the sending of emails out and the sharing to FB, etc.? Is that on my end or where you are?

One of the major advantages of Jetpack is, in addition to the actual feature, you have the ability to use the WordPress.com “cloud”.

When you write a new post, your server attaches to it a bit of metadata indicating what services should get Publicized to (e.g. what checkboxes are checked in the Publish metabox) and the post’s status in reference to WordPress.com.

Your server then pings WordPress.com and communicates to us that 1. there’s an update to the post, 2. it is a newly published post, and 3. that it needs to be sent out via Publicize, as well as typical stuff (title, author, etc).

On our end, we take that information and notify your subscribers via e-mail. We do this on our end to ensure deliverability (e.g. you don’t have to worry about if someone else hosted on the same server as you is spammy and hurting your ability for your subscribers to receive your e-mails).

We also make a connection to the various social networks and send out the post information to them. We do this because to publish to social networks, you need to have a developer account registered (e.g. “an application”) and include the various “secrets” (basically, a password) from that social network to publish as someone. Instead of asking you to create new apps on each network you want to use (in addition to your actual personal account) and program in the keys. We also process some error reporting. On your server’s end, your server determines, as part of the meta data sent to us and what’s in the source code of your site, what the title, description, image, etc should be that is associated with each post.

On your server, your scheduled post is in your database with a record to be published as close to 12:01 am as possible. When someone (anyone, a human, a Google “bot”, etc) visits your website, one of the commands that is processed is to check the database for posts that should be scheduled and then publishes it.

So, for example, if you were running a new site that no one visited yet and had a scheduled post, it wouldn’t actually go live until someone visited the site for the first time after it should be published.

I hope that make sense. Please let me know if you have any more questions. Cheers!

hi,

I too facing the same problem as I host it on bluehost and now I cant even connect these social networks through publicize.

pl. see it my site is https://turnonnet.com