Andrew Arthur Dawson

It looks like whatever the issue was is now corrected as I ran both links in twitter and Facebook Debuggers and whatever was causing the Curl error in Facebook and then connection error on twitter isn’t showing up.

I would still like to know from Jetpack’s teams knowledge if you guys know what exactly could have triggered this error and how it may have gotten fixed just for curiousness sake.

So basically it probably is all server related then and not plugin related for all of us? Or indeed on some level the server wasn’t equipped right to handle jetpack’s update and crapped out during it.

@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?

@ange21 @1dianaf can both of you please at least let me know which plugins you are using? I have my own thread going and at least am trying to see if there are any strange commonalities that link us all together? There may be none and our errors may be all different On why the update failed, but I am just a “joe user” trying to see if there are any connections? It would really help in my testing and debugging to know? @jeherve can vouch that I am a true user and been around for a while in case you think I’m some strange person bombing your forum. I’ve been on godaddy with Managed WordPress For seven years now and have had many issues with jetpack updates over the years all usually related to my server set up. Please respond.

@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?

@ange21 hey can I ask what plugins you have active? I asked this same question to @1dianaf but still am waiting on the answer. I ran into a similar problem twice and want to see if we have any plugins in common? Also what hosting do you use? I use Godaddy managed WordPress. I’m trying to see if there are any commonalities amongst us all? Also I’m using the 2016 WordPress theme. I look forward to your answers.

@jeherve I appreciate the lengthy response. Yes I agree, there has been many server issues over the years that I’ve come across. Sadly, the bulk majority have been Jetpack’s way of handling things that have in turn caused the server to not handle it because it was set up to handle it. On some level I often think that the server team at GoDaddy have probably had to evolve and reconfigure their server configs to handle Jetpack specifically.

Nevertheless, tech support at Godaddy has changed now and not to any benefit of me that’s for sure. Now, if any plugin ends up crashing my site and hoses it up, I have to go to the premium tech support and pay them to fix it for $49 and it takes them 48-72 hours. I almost had to resort to this on this last update and was arguing with the support person about it as she was telling me it was the plugins fault my site’s database was trashed after the attempted update not their fault. And supposedly now when a plugin causes this and not an error that just comes from general wordpress issues it’s going to cost money. I’m pretty upset that I have so many years deep with them and they are now nickel and diming their tech support.

And speaking of tech support, I asked for more specific details on what exactly crashed and they of course were unable to see anything more. ?? But were more than willing to have me pay money to look into it further with that premium group.

So, 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. So I guess my only thing I can do is try again and if it happens again, I’m going to have to log into FileZilla and delete the jetpack folder.

When doing the jetpack delete, let me clarify these steps with you to make sure I have this right if I have to get to this again:

1. Do I need to deactivate Jetpack first on the plugin page to do this.
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?
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?
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?

@1dianaf hey can I ask what plugins you have active? I ran into a similar problem twice and want to see if we have any plugins in common? Also what hosting do you use? I use Godaddy managed WordPress.

@sean-h i really appreciate your responses. Based upon others having full success with the upload to the new version, yes I agree there probably is a compatibility issue or weird snafu with my managed WordPress server. I have a tendency to believe it really has nothing to do though with a plugin I am using, as the ones I’m using don’t affect much at all and have been with me without changed for at least 6 months with multiple jetpack versions. For it to abruptly break with changed on my part leads me to believe that jetpack introduced something new in 9.0.2 to being this about with my specific server config. Of course it could always be a hiccup in the server going on that night I tried twice in a row and be fine if I tried again. Either way, I’m leaning towards waiting for a later version of jetpack we that is what I did back in the 7’s and it corrected itself and I personally never changed a thing. It’s funny though, I’ve not had a single issue on my WordPress in the past five years except for where jetpack is concerned. And ironically, all the tech support had said the majority of their WordPress tech support calls deal with the jetpack plugin. Go figure. I love the plugin but I don’t like how it interacts on Managed WordPress for me in Godaddy. I have a number of readers now subscribed and thousands of articles written that moving to another host or ditching jetpack just isn’t feasible for me. So I can either hope for more to fail on this to find the problem, for it to correct itself in later versions, or so just stick it out with an older version all the time. If by some chance you have the link to that other case that sounded similar can you put the link in a response as I’m not sure where it is? Thanks!

@sean-h Did you happen to see what the setup was exactly with the other case? Honestly, my hope is that more will fail so that it gets fixed. My judgment though is the server setup is causing this. For the life of me I can’t see how my configuration is causing this. I barley use plugins, I’m running a WordPress theme (2016), and I’m running current PHP and WordPress. What really could be causing my specific setup? The only weird thing about mine setup is that I’ve posted every day a text article for seven years straight so there is a lot of data. That’s about it though?

@jeherve yes indeed it is not the first time. But it’s been at least over a year this hasn’t happened with any updates with Jetpack. With the plugins I just want to make sure you don’t see any conflicts with any of them with jetpack do you? Also very single time I had issues in the last and I mean every single time it was due to a time out. Basically not enough memory resources on their server. This was a 500 internal server error both times and something I have never seen before. I don’t even know what a 500 error indicates with this update? What changed between 9.0.1 and 9.0.2 that maybe could lead to this? I read the change log and it’s like reading Greek to me. Do you have the ultimate managed word press for your test platforms and could you mimic my site with the 2016 theme to see if the update causes the issue? I know this is a lot of questions but I don’t believe it’s truly related specific to me. Maybe not enough have upgraded to the mini new version. I’m running fine on 9.0.1 and have been on everything other version since the late 7’s. Maybe your developers can contact the server people at godsddy who I can’t speak to and find out if they changed something in the server configuration? And yes, I have deleted jetpack before in the past, it just was a very challenging effort for me so I would like to brainstorm and keep this forum open to see if anyone else has a problem. For me, with not having made any changes on my site other than theme or jetpack or WordPress updates, this again frustrates me as I didn’t do anything to cause this.

@sean-h I just want to thank you for responding. I don’t have auto updates on for that very reason too. I did look at the description of the update after it crashed my site but I was unable to understand a lick of it sadly. Whatever is causing the 500 internal sever error with each attempted update is beyond me and I pray Jetpack will have some better idea. I won’t be so quick now to update to a new version I can at least say that.

@sean-h I agree with you that Godaddy can be a little mad sometimes with things. Yes they indeed do change their server configs from time to time this screwing up plugins, except the only one this has ever happened with is jetpack. Regardless, here’s the thing, I have about a 1st grader understanding of WordPress and other than hitting update for a plugin I don’t know how to do much else. So to migrate it would either be me hiring someone to do so without money that I don’t have or expertise I don’t have. Hence why I stay with Godaddy. I also do like that they are available 24/7 by phone and I have many a times been on the phone with them at times like 3am. Other competitors don’t have that kind of service sadly. So long story to end here, I’m at the mercy of both them and Jetpack to fix this with little to no expertise or money to do a damn thing about it. ??

@sean-h Well, the main difference is that you are on Siteground GoGeek which is not Godaddy and sadly Godaddy has notoriously had issues with Jetpack. Before version 7 came around, the plugin was too big and many of us on Godaddy Managed WordPress couldn’t update because of time outs. Did you know that more than 50 percent of Managed WordPress accounts are hosted on Godaddy? I’ve been with them for seven years and posted every day. To move off of them now and migrate to another platform is an expense and a lot of energy I don’t have with my lack of job and health issues. Regardless, Godaddy at least saw in the logs during the attempted update that Jetpack was trying to update the core files and that’s when it crapped out and hosed my entire site up. After trying it twice and being down for almost an hour and a half I gave up on 9.0.2 and am hoping Jetpack can figure it out as I’ve exhausted all my abilities to fix it on my end. All I know is that I’ve had zero issues updating Jetpack between the versions 7’s to 9.0.1. And other than this plugin updating and WordPress moving to the latest version, nothing has changed on my site whatsoever in over a year. I love jetpack for what it does for me but I honestly get really frustrated at the ongoing problems over the years with them and GoDaddy. Godaddy tells me it always Jetpack’s fault and jetpack always tells me it’s Godaddys fault. And I’m stuck in the middle with zero options. Ugh. Well anyway, I probably told you a lot more than you needed to know but I’m glad your update went well. Hopefully they can test their managed WordPress on godaddy and figure this out as there is nothing I’ve done that could have caused this seeing nothing has changed but jetpack in so long.

@macmanx Well that was initially my thought but when multiple providers didn’t accept the email that’s where it did not make sense. Since that happened that one night it hasn’t happened again which is why this is so strange because prior to it happening either all my emails went out Successfully or none of them. So I’m in a quandary as to why only some from multiple providers. And one of the other forum people above said someone else that night had issues too so I’m still inclined to believe it was a hiccup after your side was sending and before it actually left. Basically that the providers never got the email and the server stopped midstream on your end in a random hiccup.