Update to 9.0.2 failed…twice on Managed WordPress GoDaddy

1. Do I need to deactivate Jetpack first on the plugin page to do this.

No, no need. You can delete the plugin folder right away.

2. Is there any other folder necessary to delete for this to be successful other than the jetpack folder in the plugins, as the only other time I had to do this I followed what this guy that was communicating in the forums with you guys and he said he had to delete the .maintenance file?

Just the Jetpack folder (in wp-content/plugins/jetpack) is enough.

The .maintenance file you’re referring to is a file that’s created (then automatically deleted) by WordPress during automatic updates. None will be created here since you will not be doing an automatic update.

In general, if the .maintenance file remains after a plugin / theme / core update, it means there were server issues during the update, and you would indeed need to delete the file manually. You can read more about it here.
If you’ve experienced this in the past, it points once again to issues with your server.

3. When it is fully deleted, do you just go back to the plugins on the dashboard and select jetpack and download fresh and then activate which will ask you to connect your site with your email used for WordPress and then all my former settings are still there because they aren’t ever deleted in this process since they are stored on your end with my iCloud email address I use?

Exactly.

4. And as a last comment, not really in this setup though, why specifically do you think my site gets these often and rarely do others seem to get them on managed wordpress when my site is literally nothing other than text using a WP theme and bare bones plugins really? There are literally thousands of people probably on my platform using Jetpack and I never hear them on the forums, so why would my config do this on and off, always when I have jetpack updates, (I had this happen only once with a theme conflict and you guys acknowledged it and fixed it) especially when to put it bluntly my site is a dear diary type of setup with nothing special but my personal life in text?

That’s a great question. I don’t know. There are definitely a lot of folks using Godaddy hosting plans, WordPress, and Jetpack.

It could be a combination of reasons.

Maybe no one else runs into those issues. Maybe others who run into such issues do not post in the forums; maybe they post elsewhere (Godaddy community forums, Jetpack email support); maybe they find answers to their issues on Google and do not need to post here. Maybe you follow a different process to maintain and update themes and plugins on your site, something that would be more prone to issues.

On this, your guess is as good as mine I’m afraid.

I wish I could switch off of them and had the money to do so and wished another hosting company like you guys had 24/7 phone support as that is crucial for me as I don’t operate well with emails and waiting around for responses.

There are a number of hosting companies that may offer just what you’re looking for. Some offer phone support, others offer Live Chat support, others offer only email. You can use websites like this one to compare hosting companies and find something that would work for you.

Most hosting companies have processes in place to help you migrate your content to their platform, and things like your Jetpack subscribers would follow you wherever you go, as long as your site URL remains the same.

@jeherve thank you for taking the time to help as much as you do. I actually am on one of the original servers when managed WordPress first came out and often wonder if that’s why I deal with more problems. Either way you are most likely right, it probably is a combination of factors beyond my understanding. I’m most likely going to wait a few updates to try again as I am pretty overwhelmed right now with other things and don’t want to tackle this at the moment if indeed an issue arises. I’m running fine on 9.0.1 but may wait till later higher versions of 9 to try again. Often godaddy figures their stuff out and fixes it by the next time I try. That indeed is what happened when I waited through 10 versions of jetpack updates the last time and tried again.

Anyways I only have one last question. Where is the .maintenance file stored when I go into FileZilla and if it’s there you are staying I would have to delete it AND the jetpack folder then if it comes to me having to reinstall?

Where is the .maintenance file stored when I go into FileZilla and if it’s there you are staying I would have to delete it

You would only have to deal with this if you were seeing a big Maintenance error message on your site instead of any of the original content.

If that were the case, you would have to look for that .maintenance file at the root of your WordPress installation.

@jeherve when Godaddy does my jetpack updates it puts my system on maintenance mode and the only thing anyone sees is a white screen and a single message that says my system is in maintenance mode getting updated. When the jetpack updates finish that white screen goes away and I’m back on my dashboard where the plugin usually says updated to the new version. I’ve never looked to see if that file is there when my site is up and running normally like now. But if it is and that file is there still if I need to do the delete jetpack folder, then I should delete that too?

when Godaddy does my jetpack updates it puts my system on maintenance mode and the only thing anyone sees is a white screen and a single message that says my system is in maintenance mode getting updated. When the jetpack updates finish that white screen goes away and I’m back on my dashboard where the plugin usually says updated to the new version.

That’s indeed how WordPress updates work. The .maintenance file is there temporarily and is in charge of displaying that maintenance message.

I’ve never looked to see if that file is there when my site is up and running normally like now

It’s not. The file is only there during updates. If it were still there on your site today, you would see the maintenance message. That’s when you’d need to delete it.

I had a similar instance. A client has a GoDaddy Managed WordPress hosting package, and after the update for Jetpack, the module for toggling Protect to on wouldn’t work (mind you this was while Limited Login Attempts Reloaded which is pre-installed from GoDaddy was going wild, over 300+ attempted logins ) I got a message saying server misconfiguration contact the hosting.

So I contacted the GoDaddy, ok Jetpack I can take a hint.

GoDaddy said it’s a plugin conflict (which it may be, who am I to judge) so please turn off Jetpack and turn it back on. So I did, now after reconnecting to the same Jetpack account, Protect gave the same message and now Brute Force was off. Server misconfiguration error.

Thankfully, I found your post, I rolled back to Jetpack 9.0.1 (for anyone else who may encounter this issue, just delete Jetpack, go to add Plugins > Jetpack > Advanced View > Previous Versions I ran with 9.0.1 and bada bing, bada bang I’m back cooking with gas.

Thank you Andrew Arthur Dawson, if we ever cross paths, coffee on me.

• This reply was modified 3 years, 11 months ago by Jay Lopez. Reason: typos