Moderator
t-p
(@t-p)
– Please check the error logs on your server for a more specific error message and see why it’s failing. If you need help locating them, ask your hosting provider to help you with that.
Is that something I can find myself? Unfortunately, GoDaddy is not the best as helping me with any WordPress issues. Where are the error logs normally kept with WordPress postings? And if a server that my domain is hosted on for my WordPress is running sluggishly, in other words, response time is greatly delayed from getting the server to process a request, could that cause an issue in the scheduled posting if someone goes to my page?
My theory is that I have a “Missed Schedule” and normally if the server is responding at normal speed, someone comes to my site and immediately it publishes the scheduled post, but if the server is not responding, maybe it’s causing a delay in getting this request out there? Have you seen this before?
I’m only wondering though because I did not have any issues with WordPress 4.5 at all with any of my postings and I haven’t added or removed or changed any plugins between the two. So that’s what lends me to believe there might be an issue with 4.6?
My site is http://www.thetwelfthstep.com by the way.
PS – I’ve also noticed some response time issues with WordPress.Org as well like when I went to update my post here, I got a server not responding message several different times. Are there problems ever with the WordPress servers?
Andrew, we also have a client who is hosting their website on GoDaddy’s managed WordPress hosting and is seeing the “Missed Schedule” issue. Has there been any update on your end regarding what’s going on? Did you work with GoDaddy to fix the problem?
Thanks!
Just curious, just your client use Jetpack Jonathan? I’ve been working with Jetpack as I believe the issue has been on their end. But I may be wrong on that. As for talking to GoDaddy, I have found their tech support to not be very helpful. They truly only make sure my site is up and running and always point me in the direction of the wordpress forums to look for answers. They aren’t staffed to undertsand the complexities of wordpress unfortunately. But what I have noticed is that since upgrading to WordPress 4.6 and Jetpack went to 4.2. I’ve had issues a constant basis with my scheduled postings. Let me know if your client uses Jetpack ok?
Thanks for the response Andrew. Our client does use Jetpack. In particular, they use the Monitor and Widget Visibility features. What makes you think that the issue is caused by Jetpack?
Your comment about GoDaddy support has definitely been in line with our experience so far on their WordPress hosting platform as well.
Have a good one.
I was told by Jetpack that GoDaddy uses caching and with the new WordPress updates and Jetpack updates, missed schedule postings are not getting out till the caching window is refreshed. In other words, however long GoDaddy’s caching is say 10 minutes then it won’t be until the next person comes after that ten minutes had passed that the blog will post. Any time before that the viewer is just looking at a cached page unfortunately. It’s a limitation of GoDaddy because they use caching instead of a constant refresh on their sites. It’s probably done that way for speed on the servers they use because they put a bunch of people on one server. I’m guessing your client is probably also on managed WordPress with them and the basic level right?
Thanks Andrew. Our client is using their managed WordPress setup, so it’s likely something with their configuration. Caching is used on a ton of hosting platforms and have never seen this issue, so it must be a specific system within GoDaddy.
Jonathan
Wired Impact
Has anyone had any success getting the scheduled blog postings to go out to the subscribers or the social media? @wiredimpact @jg-visual
I spoke with GoDaddy today and they restarted the Cron for my server but I don’t believe that is really going to do anything because they told me that the Cron was running fine and had no issues on their side. I’m still convinced this is a Jetpack issue on their 4.3 software but of course I could be far wrong too…
Unfortunately, we don’t have any more information. Our client connected with GoDaddy directly. Since we haven’t heard anything I would assume it’s fixed, but I don’t know for sure.
Good luck.
Jonathan
Just a quick update to anyone who’s following this forum. As of Jetpack 4.2.2, I’m still getting the same scheduled issues with my GoDaddy hosted blog. The blog posts fine on my site, but the publicize doesn’t work in getting the subscribers their email nor the social media. Hopefully one day this will get resolved. I honestly wish GoDaddy was a little better in their Shared Environment. I truly think all of this breaks down to their caching system.
Hi, please forgive the novice level response here….
We’ve had the same problem with Go Daddy with daily posts missing the scheduled publishing time usually between 5am-6am daily.
Finally got a response that made some sense.
Go Daddy uses a “virtual cron” which for us meant that it was “asleep” at the time our posts would fire and to not have the problem they say all we need is a page request (front end or wp-admin) to have the virtual cron activate.
Option A – have a page request execute before the scheduled publish time
Option B – move to CPanel hosting and have 100% active “real” cron all the time.
Any input to resolve this would be greatly appreciated.
@gaskinner I know your pain as I’ve been dealing with this since September of last year. You are correct on your two ways to deal with the issue. Thankfully there is a plugin created by a GoDaddy Managed WordPress user that helped with this. It’s called Scheduled Post Trigger and has worked to overcome the cron/caching issue that GoDaddy has. But, I still have a problem with Jetpack and my scheduled post working with GoDaddy’s setup. My social media still doesn’t get fired off when it’s publicized but Jetpack says it’s being worked on. They have made some progress and hopefully on the next release it will be fixed. 🙂
Thanks Andrew! If that plugin has worked for you we’ll go ahead and give it a try.
