Support » Fixing WordPress » Updating jetpack broke my wordpress

  • Hi all, I always try to keep updated my WordPress for security matters. This morning Jetpack asked me to update from 4.7.1 to 4.8. The update was successful (based on the message I read at the end of the update). Once I refreshed my site, it started not working anymore. I haven’t got any clue on what exactly happened. Can you help me in restoring it back?

    The website is this one:

    I entered in the database and I can see that all the posts are still there. In addition I can see that if I refresh to a certain article I wrote in the past I get this error:

    Warning: Can’t set CURLOPT_CUSTOMREQUEST before CURLOPT_URL in /membri2/infernusweb/wp/wp-includes/Requests/Transport/cURL.php on line 348

    I am not sure if this is the cause of the problem, cause this warning was already there since couple of days, before updating jetpack. However it kind of tells me that something is going on there, but it fails to display. I honestly don’t know what to think about this issue. Please help me!


Viewing 8 replies - 1 through 8 (of 8 total)
  • To add to this. Is not only the front part of wordpress that doesn’t work. I can’t even access to the dashboard, to the update-core and so on.
    I guess that removing jetpack would bring back my wordpress. But unfortunately I can’t act since I cannot access to the control panel of wp.
    I had my site (trhough jetpack) connected to where I have another blog, but does not receive any information from my site anymore, so I am kind of handcuffed for the moment.


    Hi @angelosalatino,

    It is always recommended to take a backup copy of the site before updating.

    You can download the older wordpress file and revret back.. Below are the link..

    If you need any technical help or have further query, please let me know.


    Hi @angelosalatino,,

    It seems something is conflicting your website. You need to revert back your website using the COntrol panel of the hosting.



    • This reply was modified 1 year, 11 months ago by  Sayan Naskar.
    • This reply was modified 1 year, 11 months ago by  Sayan Naskar.
    • This reply was modified 1 year, 11 months ago by  Sayan Naskar.
    • This reply was modified 1 year, 11 months ago by  Sayan Naskar.
    • This reply was modified 1 year, 11 months ago by  Sayan Naskar.

    Hi @prasadneeraj,
    unfortunately my hosting service allows me to restore the database only. I made a backup of the corrupted database and now I restored the copy my hosting saved on the 2nd of april. It didn’t improve the situation. The website still does not respond. Everything is white.
    I have another copy of the database only of the 20th of march, but I don’t know if it would make any improvement.
    I was thinking that maybe there is a mismatch between the version of wordpress using that database on the 2nd of april with the one I currently have. How can we check this from the database? If I check the version.php it says I have the 4.7.3, but I am not sure which one I had on the 2nd of April (although is only 3 days ago 🙁 ).

    If I download the right version, shall I just upload the files or reinstall everything?


    Actually what I am thinking is that maybe if I restore the database to the 20th of March I would get rid of jetpack reference into the database since I installed it only last week.
    What do you think about it? Does it make any sense?

    Moderator Steven Stern


    Support Team Volunteer

    PLease see this and see if their solution helps:

    If not, the developers and users of that theme/plugin would be the best people to ask. You can reach them here:

    Hi @sterndata,
    that’s fantastic. Thanks for the lead. The website now works again.
    I basically had to rename the folder of Jetpack. Then the website started wotking again and then I remove the jetpack plugin.

    The website now is fine, it works.

    Thank you all for the precious help.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Updating jetpack broke my wordpress’ is closed to new replies.