• Resolved bjf2000

    (@bjf2000)


    Ever since the upgrade to 13.0 three days ago, Jetpack has failed in its nightly backup: “We could not back up your site because it appears to be offline.” So, three times in total.

    This could be a coincidence, but I’m guessing that it probably isn’t because it had been fine until 13.0. I don’t see anything in the release notes about it, however. Is it plausible? I’d like to eliminate that angle before investigating others.

    Yes, VaultPress Backup is still listed as “Active” on our site. Yes, the site is active. No, I’m not aware of any changes from Cloudflare or Wordfence or our host which could also cause this, but that’s where I’ll look next depending on the above answer.

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter bjf2000

    (@bjf2000)

    So, after a 4th consecutive failure, I reverted to 12.9.3 and then waited for the next scheduled backup that night.

    It worked. No way that’s a coincidence too.

    So I’ll just stay on 12.9.3, and when 13.1 comes out look at the release notes for it to see if there’s a hint of the problem.

    Plugin Support Gaurav (a11n)

    (@gaurav984)

    Hi @bjf2000,

    Could you please post your site URL here so that we can have a look?

    If you want it to remain private, you can also contact us via this contact form:

    https://jetpack.com/contact-support/?rel=support&hpi=1

    If you choose to reach out directly, please include a link to this thread.

    Thanks!

    Thread Starter bjf2000

    (@bjf2000)

    It’s working with 12.9.3. Given the other reports of other connectivity problems with 13.0, I think we know what the problem is.

    We are having this same problem on our site – can you tell me how you reverted to the prior version? I can do it from the last backup, but then would I need to recreate any site changes since then manually?

    Thread Starter bjf2000

    (@bjf2000)

    Yes, with this:

    https://wordpress.org/plugins/wp-rollback

    Then on your plugins page just ensure that auto-updates is disabled for Jetpack.

    • This reply was modified 4 months, 2 weeks ago by bjf2000.

    Thanks, the backup was broken on 13.0 with the same message, and rolling back to Jetpack 12.9.3 makes it work again.

    Thread Starter bjf2000

    (@bjf2000)

    13.1 is out now, which I guess I’ll test despite the release notes here and here not hinting of anything to do with this. It’ll be very interesting if it still doesn’t work.

    Thread Starter bjf2000

    (@bjf2000)

    Incidentally, I don’t know if this has happened to anyone else as a result of subscribing to notifications for this thread only, but I’ve been receiving notifications somehow for other things related to Jetpack, and the emails offer no hint about how to stop them. They look like this and are from jetpack/tags and jetpack/trunk.

    View post on imgur.com

    Thread Starter bjf2000

    (@bjf2000)

    Nope, 13.1.1 has the same problem. Someone at Jetpack ,must know what changed and why, since this is pretty binary.

    Thread Starter bjf2000

    (@bjf2000)

    According to support, this is indeed due to recent changes on their end. They suggest multiple ways to fix it.

    1. Install this, which was just updated with the fix: https://wordpress.org/plugins/jetpack-backup
    2. Wait for the next version of Jetpack, due in early March
    3. Add your FTP, SFTP or SSH server credentials in Jetpack Cloud
    Plugin Support Joseph B. (a11n)

    (@tamirat22)

    Hello @bjf2000,

    Were you able to address the backup issue by following the temporary suggestions you got from our support team?

    @gslin & @delraycitizen, please start a separate thread per the forum guidelines here. You can do so from here: https://wordpress.org/support/plugin/jetpack#new-post

    Thank you!

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hello @bjf2000,

    Do you have updates about that? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

    Thread Starter bjf2000

    (@bjf2000)

    If that’s a priority, I guess it can be, but it is strange to me how an issue of this level has gone completely unmentioned anywhere that I’ve looked. The release notes for the backup plugin I mentioned above which supposedly has the fix already doesn’t even mention it. So I imagine that the release notes for the Jetpack plugin itself next month won’t either. This doesn’t seem right or plausible.

    Thread Starter bjf2000

    (@bjf2000)

    Incredibly, hours after writing that, Jetpack 13.1.3 was released:

    “Backup: write helper script to ABSPATH by default to avoid backup failures.”

    It took some detective work, but I traced that back to this:

    https://github.com/Automattic/jetpack/pull/35508

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @bjf2000,

    Massive apologies for the late reply in catching up with this thread. Do you still need help with this?

    If so, given you’re a paid user, you’re welcome to write to us directly via email via contact form. Please include a link to this thread and let me know when you did it so I can track down the ticket. Thanks!

Viewing 15 replies - 1 through 15 (of 15 total)
  • You must be logged in to reply to this topic.